Data methodology
Robotaxi Pulse shows three separately labeled datasets: official TxDMV registration counts, Tesla’s published robotaxi safety report, and company-reported Tesla service cities. It does not predict fleet growth, launch dates, or revenue, and it does not add those figures into one fleet size.
Where the data comes from
Commercial automated vehicle operators authorized in Texas publish vehicle lists through the TxDMV TxMCCS TruckStop public API. We store the raw JSON response for every sync.
What “Updated” means
On the Official Registry page, Updated … ago is the time of this app’s last successful sync: we checked TxDMV, parsed the VIN list, and stored a verified snapshot. It is not an official TxDMV publish timestamp, and it does not mean the registration count changed at that moment. On the Safety Report page, Last checked … ago is the last successful read of Tesla’s safety page. The report period and city dates on that page are the dates Tesla printed, not the time we fetched them.
How changes are detected
Each sync compares VIN sets between consecutive verified snapshots. Added and removed VINs produce a change record. Counts are derived from those VIN lists — never estimated.
Three datasets under Robotaxi Pulse
Official Registry (/) shows official TxDMV VIN registration counts. Tesla Safety Report (/safety) shows company-reported figures from Tesla’s robotaxi safety page: city cumulative miles, the SGO spreadsheet, and the report’s own totals. The mile added between two dates is the difference Tesla published, labeled with the actual span. The three headline counts are Tesla’s figures, not a recount of the spreadsheet. When Tesla prints human-driver expected collisions beside those counts, the Safety Report shows them for that edition only. Pace is Tesla’s published counter rate for the matching city-total edition; the live displayed mileage counter itself is not stored, and no daily or seven-day series is derived from it. Tesla Service Cities (/cities) lists company-reported service areas. Its map marks city centers, not service boundaries or geofences. Do not add registration counts, safety miles, or city counts into one total.
When the official source does not update
If a sync fails or returns unusable data, we keep the last verified snapshot, mark the source unhealthy, and do not publish new values. A failed sync is never shown as “no change.”
Current sync status
- Health
- healthy
- Last successful sync
- Nov 1, 2026, 12:00:58 PM
- Last attempt
- Nov 1, 2026, 12:00:58 PM
- Source
- Texas DMV TxMCCS TruckStop
Disclaimer
This app is not affiliated with or endorsed by Tesla, Waymo, TxDMV, or any automated vehicle operator. Registration counts reflect vehicles listed under a commercial AV authorization — not necessarily vehicles actively serving riders at any moment.