Cybercab vs. the Calendar: A Delivery Target, a Federal Audit, and Three Fleet Counts That Do Not Agree

The Cybercab now has a calendar, and the calendar has teeth. On one side of it stands a delivery target spoken aloud on an earnings call. On the other stands a federal audit with a sworn deadline nine days later. Between them sits a fleet that is three different sizes depending on whose count is used. This page lays the three pieces side by side, each with its name on it, because the Cybercab story from here to December is not a product story — it is a race between a promise and a paperwork deadline.

Label: Reported for the call statements and the audit’s status, per The Fox Daily (October 22, 2026) and the TrendInTech Cybercab timeline (updated October 2026). Label: Claim for the delivery target and for Tesla’s fleet count, both of which are Tesla’s own statements about Tesla’s own plans and vehicles.

The target: customers by the end of 2026

On Tesla’s Q3 call, October 21, 2026, VP of Vehicle Engineering Lars Moravy put the date on the record: Tesla is trying to get Cybercabs to customers by the end of this year, 2026 — with a limited rollout first.

Grade the sentence the way this site grades every forward statement:

• It is a target, spoken by an executive on an earnings call. It is not a delivery, a production count, or a filing.
• The word “customers” is the load-bearing word. A Cybercab operating in a Tesla-run fleet is a service vehicle; a Cybercab delivered to a customer is a product. Moravy’s sentence claims the second, harder thing, on a deadline roughly ten weeks from the day he said it.
• The qualifier is also on the record: limited first. Whatever arrives by December 31 will arrive in small numbers, by the statement’s own terms.

The target now exists where this site can grade it: attributed, dated, and checkable on January 1.

The audit: answers due October 30

Running against the target is an open NHTSA audit of how Tesla self-certified the Cybercab. The object of the audit is the certification itself — the process by which a manufacturer attests that its vehicle meets federal safety standards — applied to a car built without a steering wheel, without pedals, and without mirrors: the three control and visibility fixtures the standards were written around.

Tesla’s sworn answers are due October 30, 2026.

Two things about that date deserve plain statement:

• Sworn is not a synonym for “submitted.” Sworn answers are given under penalty for their truthfulness, to a regulator, in an open proceeding. What Tesla says on October 30 will be the company’s formal position, quotable back to it in every later round of this fight.
• The deadline sits between the promise and the promised date. The audit does not need to conclude for it to shape the delivery story; its questions alone define what Tesla must be able to say, in writing, about a wheel-less car before it hands one to a customer.

Label: Confirmed as to the audit’s existence and the October 30 due date as reported; the audit’s eventual findings are not in the record and are not predicted here.

Three counts, printed side by side, never merged

How many Cybercabs are operating in Austin — the fleet already on the road ahead of any customer delivery — depends entirely on who is counting. The record carries three figures. They are printed here in parallel and are not averaged, reconciled, or settled on this page:

• 300-plus — Tesla’s own figure, stated October 10, 2026. Label: Claim (the manufacturer, counting its own fleet).
• 319 to 349 — the Texas registry figures: a range, not a single number, drawn from state registration records. Label: Reported (a public registry, as compiled in the coverage).
• Far fewer — third-party trackers, counting vehicles observed in active service, arrive at a materially smaller number than either of the above. Label: Reported (independent counts, methodology theirs).

The spread itself is the finding available today. A manufacturer count, a registration count, and an in-service count measure three different things — vehicles claimed, vehicles registered, vehicles seen working — and a reader who merges them into one number has manufactured a fourth figure that no source published. When Tesla’s sworn answers land on October 30, this table is the first thing to check them against.

Dallas, in November

The expansion is already scheduled into the gap between the deadline and the target: Tesla has announced a Dallas expansion for November 2026. Label: Reported. A second city widens everything this page is tracking — more registered vehicles for the Texas count, more observed cars for the trackers, and a second market in which the gap between the three counts can be measured instead of argued.

The calendar, in order

• October 21, 2026 — Moravy’s delivery target, on the Q3 call record: customers by the end of 2026, limited first.
• October 30, 2026 — Tesla’s sworn answers to NHTSA due in the self-certification audit.
• November 2026 — Dallas expansion, as announced.
• December 31, 2026 — the date the Moravy target is graded against.

What this page is watching for

Three documents would change this story from claims to findings: the text of Tesla’s October 30 answers; the first customer-delivery record that matches the target’s own wording; and a fleet count on which the registry and the trackers converge. Until at least one of those exists, the Cybercab’s position is the one its calendar gives it — a car with no steering wheel, promised to customers in ten weeks, whose maker owes a federal regulator sworn answers in nine days.