Open tracker data
Download sourced robotaxi deployments as CSV or JSON. Check the coverage, field definitions, verification dates and CC BY 4.0 attribution terms.
Download current records
The current extract contains 25 operator–city records covering 14 cities. Each row describes the most recently verified stage for one operator in one city.
Use CSV for a spreadsheet and JSON for an application. Both formats include source links and the checked date. The public feed can be cached for up to one hour.
Field definitions
| Field | How to interpret it |
|---|---|
| City and operator | A city can have several rows. Count city–operator pairs for deployments, and distinct city slugs to count markets in our coverage. |
| Service status | Announced, testing, employee only, public free, public paid, paused or ended. Read the service-area note for invitations, neighborhoods and access restrictions. |
| Since date | The first confirmed day of the recorded status when known. A missing date means the evidence did not establish an exact day. |
| Onboard monitor | Yes, no, mixed or unknown for the specific local service. Remote assistance and the presence of an onboard monitor are separate observations. |
| Fare note and owner enrollment | Fare notes describe published rider terms. A private owner needs a separate enrollment agreement and settlement terms. |
| Source and verification date | The evidence behind the record and the day it was reviewed. Read a dated source in its original geographic and operating context. |
| Latitude and longitude | Approximate WGS84 city centers from GeoNames. Coordinates locate the city on a map. They cannot identify a service boundary or confirm a pickup. |
Coverage and verification
100% (25 of 25 deployments) were checked within the past 30 days.
The tracker is a curated sample of documented deployments. It covers passenger fleets and selected testing programs. A missing operator or city means the sample has no reviewed record for that pair. Use the timeline to see published changes to previously observed stages.
An operator announcement, a regulator record and a community observation each answer a different question. A historical vehicle count cannot measure how many cars are available for dispatch today. The examples below preserve those distinctions.
Dated evidence
| Subject | Reported observation | What it establishes | Source |
|---|---|---|---|
| Austin fleet observations | Electrek cited community observations of roughly 17 active unsupervised Tesla vehicles in Austin in July 2026. | Community estimate for one period and one city. Sightings can miss vehicles. | Community data on Austin’s fleet as Tesla adds Florida cities |
| Tesla fleet activity | Tesla’s quarterly update reported more cumulative unsupervised miles and the introduction of Cybercab rides in Austin on September 3. | Company-reported activity during the third quarter. Mileage measures something different from an observed vehicle count. | Q3 2026 update, including Robotaxi operations |
License and attribution
Reuse the tracker compilation under CC BY 4.0. Credit RobotaxiProfit and GeoNames for the place coordinates, link this dataset and the license, and state any changes. Keep the source URLs so downstream readers can check each observation.
Sample credit — RobotaxiProfit deployment tracker, with city coordinates from GeoNames, CC BY 4.0. Accessed on the date of your download. Add a note if you filtered, transformed or combined records.
Original articles, operator marks and map tiles retain their own terms.
Creative Commons Attribution 4.0 International · GeoNames geographical database
Sources
The Robotaxi Profit Report
Get the week’s verified service changes and the numbers behind them.