Where these numbers come from
Cybercab Fleet Operator answers one question: if you bought a self-driving taxi and ran it as a business in your town for ninety days, what would happen to your bank account? It is a planning tool, not a prediction, and this page is the whole answer to "says who?"
Every figure below was read out of the numbers the game actually runs on, or out of the live research behind each city. None of it was typed in by hand, which is the only way a page like this stays true after the thing it describes changes.
Built 2026-09-14 from the register in this copy of the game and from the live city research. The page re-checks both when you open it, and says so below if either has moved on.
The honest split
The model runs on 184 numbers. Here is exactly how many of them anybody else can vouch for.
Three quarters of it is ours. That is not a confession, it is the shape of the subject. Nobody has ever run a privately owned robotaxi, so there is no trade body publishing what one earns, what it costs to insure or how often it gets stuck. The alternative to an estimate here is not a fact — it is silence.
What we can promise instead is that every estimate is labeled as one, carries its reasoning, and can be replaced by yours. 144 of the 184 are editable inside the game, and changing one changes the model immediately.
A season in a metro runs on 114 of these; a season in a small town runs on all 184, because a town’s own geography — its radius, how far a fare goes, how fast the traffic moves — is on the list too. The register audits itself every time it loads: a published figure that carries no dated document, arithmetic with no working shown, or an estimate with no reasoning is a failure. It currently reports 0 failures.
What the 184 numbers are about
The same figures as the bar above, grouped by what they describe.
| The car | 10 — 6 published, 3 worked out, 1 ours |
| The permit | 5 — 5 published |
| The deal you took | 9 — 3 worked out, 6 ours |
| The fares | 6 — 6 ours |
| Running costs | 7 — 7 ours |
| Cleaning | 5 — 5 ours |
| Premises | 9 — 9 ours |
| Electricity | 5 — 5 ours |
| A heat advisory | 5 — 5 ours |
| Running out of charge | 7 — 7 ours |
| Demand | 4 — 4 ours |
| The weather | 3 — 3 ours |
| People | 1 — 1 ours |
| Penalties | 3 — 3 ours |
| The rating | 16 — 16 ours |
| How often things go wrong | 13 — 13 ours |
| What the car is worth | 3 — 3 ours |
| The season | 3 — 3 ours |
| The town | 70 — 6 published, 24 worked out, 40 ours |
The car itself is the best-documented thing in the subject and none of it is ours: battery, efficiency, motor, weight and seats come off one EPA certificate. The permit rules come off one Nevada Transportation Authority order. Those are also the two groups you cannot edit, because a certificate is not local knowledge.
How a town gets researched
21 towns and cities have been researched so far, and the same machine does every one of them. It runs in three passes, and the order matters.
Anything the United States government already publishes for every city in the country is taken straight out of the national file. Nobody is asked, nothing is searched for, and there is no page that could be misread.
- Census Bureau — Gazetteer place files, subcounty and county population estimates, and the American Community Survey summary files. 24 files.
- FAA — commercial-service enplanements, and the national airport list. 2 files.
- EIA — the Electric Power Monthly state price tables and Form 861. 3 files.
- NOAA — 1991-2020 monthly climate normals, one file per weather station. 91 files.
- BLS — the May 2024 Occupational Employment and Wage Statistics national and area files for vehicle cleaners, and the area definitions that decide which OES area a town falls in. 3 files.
The town is matched to its row by a code, never by its name — a Census place or county FIPS number, an FAA airport identifier, or a coordinate. Names are how you end up with the wrong Springfield. Across the 21 towns, 879 of the 1,656 researched numbers came out of these files, from 123 distinct downloads shared between every town in a run.
What is still researched is the LOCAL STORY, and it is researched because it is real, published and findable: the utility's time-of-use split (a filed tariff, not a table), public fast-charge prices, the visitor economy, the state's minimum liability statute, the city's own parking schedule, and the named demand generators -- hospitals with their bed counts, colleges with their enrolments, the venue that fills the town. That is the half of a pack no federal file will ever carry, and it is the half worth having: Dover, Tennessee is a town of 1,918 people in the federal files and nothing more, and what makes it interesting is that 84% of its rides are visitors to Fort Donelson National Battlefield.
Every record the model returned as 'sourced' had its cited URL fetched. The page had to load, and the figure had to be in its text within 400 characters of one of the record's own keywords. Anything that failed was demoted to 'estimated' with the failure written into its math.
Across the 21 towns 301 citations were checked. 210 passed. 91 failed and were demoted to labeled estimates, which is 30% of everything the model claimed to have a source for. A figure that loses its citation does not quietly stay a fact.
Where a demoted figure was feeding another one, the second is demoted too and says why. That happened ten times. 59 holes are written down across the six packs — things the research could not establish, recorded rather than papered over.
Re-running the same research used to come back with materially different answers, and those answers drive the whole demand estimate. 5 of them were taken off the model altogether and are now computed from a pinned national survey and measured Census ratios. What judgment remains is asked 5 times and reported as the middle answer with its spread. Across all 63 of those figures the typical gap between the highest and lowest answer is 1.25 times, and the worst is 2.50 times. That is the honest width of the part of this that is judgment.
The cross-check: where we can be caught out, we let ourselves be
The demand estimate is the number everything else hangs off. Where somebody publishes a real trip count for a town, we build ours without looking at theirs and then put the two side by side. Where nobody publishes one, we say so and name the five places we looked.
Of the 21 towns researched: 1 had a published figure we landed close to, 2 had one we did not, 17 have no published figure at all, and 1 is a gap in our own work.
Alturas, CA none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 21 rides a day, and it stands on its own arithmetic with nothing to check it against.
Buffalo, NY none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 13,661 rides a day, and it stands on its own arithmetic with nothing to check it against.
Chicago, IL agree
Published paid-ride count: 250,000 a day, published 2026-07. Our chain, built without ever seeing that figure, comes out at 235,615 a day — within 6% of it.
Clifton, AZ none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 14 rides a day, and it stands on its own arithmetic with nothing to check it against.
Cody, WY none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 169 rides a day, and it stands on its own arithmetic with nothing to check it against.
Colorado Springs, CO none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 18,346 rides a day, and it stands on its own arithmetic with nothing to check it against.
Columbia, MO none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 1,781 rides a day, and it stands on its own arithmetic with nothing to check it against.
Dover, TN none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 32 rides a day, and it stands on its own arithmetic with nothing to check it against.
Ely, NV none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 122 rides a day, and it stands on its own arithmetic with nothing to check it against.
Las Vegas, NV disagree
Reported taxi trips (cross-check): 35,616 a day, published 2025-12. Our chain, built without ever seeing that figure, comes out at 93,874 a day — 2.6 times theirs.
We do not hide this one. The two disagree, the pack records it as a hole, and the demand estimate for this city should be read as an order of magnitude and nothing finer.
Malta, MT none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 8 rides a day, and it stands on its own arithmetic with nothing to check it against.
Nashville, TN disagree
Published paid-ride count (cross-check): 10,110 a day, published 2025-08. Our chain, built without ever seeing that figure, comes out at 38,187 a day — 3.8 times theirs.
We do not hide this one. The two disagree, the pack records it as a hole, and the demand estimate for this city should be read as an order of magnitude and nothing finer.
Presidio, TX none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 12 rides a day, and it stands on its own arithmetic with nothing to check it against.
Quincy, IL not asked
This is a hole in our own work, not a finding about the town. The research never came back with a "published trip count" record at all, so we do not even know whether one exists. It was never asked, and we are not going to dress that up as "there is no figure".
Our estimate of 450 rides a day is therefore unchecked.
San Buenaventura (Ventura), CA none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 1,206 rides a day, and it stands on its own arithmetic with nothing to check it against.
Sarasota, FL none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 4,183 rides a day, and it stands on its own arithmetic with nothing to check it against.
Scott City, KS none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 21 rides a day, and it stands on its own arithmetic with nothing to check it against.
Stillwater, OK none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 491 rides a day, and it stands on its own arithmetic with nothing to check it against.
Wichita, KS none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 6,152 rides a day, and it stands on its own arithmetic with nothing to check it against.
Winner, SD none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 26 rides a day, and it stands on its own arithmetic with nothing to check it against.
Worland, WY none
Nobody publishes a trip count for this town. We say so, and we name what was searched rather than leaving "no data" to mean "we did not look".
Our own estimate is 25 rides a day, and it stands on its own arithmetic with nothing to check it against.
What we know is weak
A methodology page that only lists strengths is marketing. These are the four places where, if this tool is wrong for your town, it is most likely wrong here.
Insurance has no anchor at all
Insurance, first car, $340 a month. In the register’s own words:
There is no published premium anywhere in this. It is bracketed between two things we do know and nothing more.
The depot rent was sized against the game, not a lease
Leased bay, Sunset Rd — rent, $850 a month. In the register’s own words:
That is a game-design decision wearing a dollar sign, and it says so on its own card.
One Quincy figure is doing the work in every town
How much of an online driver’s time is on a ride: 45%. It decides how many cars are already online competing for the work, and therefore how much of it reaches yours. No researched pack overrides it, so the same estimate is running in all 21 towns.
We measured what it is worth. Replaying 24 fixed-seed ninety-day seasons, a season that finishes $10,079 better off on our 45% finishes $5,623 at 25% (44% worse) and $12,838 at 70% (27% better). One number nobody publishes moves the answer by about half. Run node _town.js sens and you get the same table.
The judgment that is left still wobbles
The demand figures a language model is still asked for are drawn 5 times each. Across all 63 of them the typical highest-to-lowest gap between identical runs is 1.25 times, and the worst is 2.50 times. Taking 5 variables off the model and computing them instead is what brought it down to that; it did not bring it to zero, and pretending otherwise would be the easiest lie on this page.
Every number is editable. Change these first.
Open Every number behind this game inside the game, tap any figure, and type your own. It goes into the model straight away and stays in your browser. Nothing is sent anywhere — and if you then put a season on the board, it goes up marked as run on custom numbers, because a season played on different figures is not comparable with one that was not.
These 5 are the ones whose own reasoning admits that a figure you know beats ours:
Insurance, first car
Leased bay, Sunset Rd — rent
The furthest a fare goes
Fares a day in the whole town
Hired rides one visiting party takes
That list is not hand-picked. It is every editable record whose reasoning contains "most worth replacing", "better than ours", "change it here" or "if you know" — matched against the register when this page was built.
What one town costs to research
Between $0.00 and $5.30, measured on the run that actually produced each pack. All 21 together came to $57.30.
| Alturas, CA single-radius town | $0.00 |
| Buffalo, NY multi-district metro | $0.00 |
| Cody, WY single-radius town | $0.00 |
| Colorado Springs, CO multi-district metro | $0.00 |
| Columbia, MO single-radius town | $0.00 |
| Nashville, TN multi-district metro | $0.00 |
| Sarasota, FL multi-district metro | $0.00 |
| Stillwater, OK single-radius town | $0.00 |
| Worland, WY single-radius town | $0.00 |
| Las Vegas, NV multi-district metro | $3.97 |
| Clifton, AZ single-radius town | $4.01 |
| Dover, TN single-radius town | $4.15 |
| Quincy, IL single-radius town | $4.74 |
| Ely, NV single-radius town | $4.77 |
| San Buenaventura (Ventura), CA multi-district metro | $4.78 |
| Wichita, KS multi-district metro | $4.93 |
| Winner, SD single-radius town | $5.06 |
| Chicago, IL multi-district metro | $5.17 |
| Malta, MT single-radius town | $5.17 |
| Scott City, KS single-radius town | $5.25 |
| Presidio, TX single-radius town | $5.30 |
| All 21 | $57.30 |
190 model calls and 1,270 web searches across the 21, and about 488 minutes of wall clock across the 20 that recorded it. The federal files are free and are downloaded once and shared, so most of that money buys the things no national file carries: the local electricity tariff, what a detailer charges, what a bay rents for, and who fills the town on a Saturday.
measured when the research actually ran on 2026-09-09; rebuilding the pack from the saved answers costs nothing
What this page is not claiming
The game is not a forecast of Las Vegas, Quincy or anywhere else. The fares, the network’s cut, the settlement lag, the loan terms, the insurance, the cleaning prices, the depot rents, the wear per mile, the penalties, how often things go wrong, and every curve describing how a district answers heat or rain — those are ours. They are tuned to make the decisions interesting. Do not quote them at anybody.
Tesla has published no Robotaxi fare table, no owner-operator revenue share and no Cybercab price. The only price on the record is Musk’s October 2024 "below $30,000". The widely repeated "$25,000" is not sourced to Tesla and this game does not use it. Nobody is running a privately owned Cybercab anywhere today; the premise is fiction built on a real statement.
Inside the game, 23 constants are tagged sourced and name their document, 4 are arithmetic on those, 3 are stated as approximate geography, and the rest are tagged ours in the source code itself. The simulation is version 1.5.0.