DatabaseDefinitionsAuthorized Vehicles

Authorized automated vehicles

How many robotaxis is each company legally permitted to operate?

Reporting obligations behind it
1
The filings a company is required to make that this figure is built from
Known biases ledgered
2
Each carrying the direction it pushes the figure, rather than a warning that data may be imperfect
Of those, unsigned
Entries where the record does not say which way the error runs

Formula

Unit: vehicles

The count each operator has registered with a state, on the most recent observation.

What it is built on

  • The Texas state registry of authorized automated vehicles

Bias ledger

Each known problem with this number, and which way it pushes it. A signed direction is more useful than a warning that data may be imperfect.

Effect
Permission, not activityoverstatesA registered vehicle may be in a depot, running with a safety driver, or not running at all. Treat the count as a ceiling on activity, never a measure of it.
One stateunderstatesTexas is the only state publishing a live per-operator count. Vehicles operating elsewhere are absent.
No rows match this filter.
Direction is the sign of the error, not its size: an overstating source pushes the figure up, an understating one pushes it down, and a direction unknown means the record does not say which.

How it is computed

Every step that changes the answer, in the order it happens. Nothing here is a summary of a longer method: this is the method.

  1. Take the most recent observation of the state registry.
  2. Read each carrier's registered vehicle count off that observation. Nothing is summed across observations, because a later count replaces an earlier one rather than adding to it.

Not for

A per-mile safety divisor. Vehicle-days measure permission; dividing crashes by them produces a number in the wrong units.

← All metrics and the nine marks