$ROBOCAR
Complaints about driverless cars in San Francisco
700.0% flaton the month before
complaints in Oct 2026Up 8% from 65 in Oct 2025
Quiet. 70 complaints in Oct 2026, flat on the month before.
From May 2025 to Oct 2026.
How it is counted
Normal46 to 70
Highest100Dec 2025
Unusual months0
- Counts
- Complaints about driverless cars made to San Francisco 311 in a month (service name Autonomous Vehicle Complaints), by the date each was made. Every complaint counts. Counted from May 2025, the first full month of the category.
- Why it is here
- San Francisco files fifty to a hundred complaints a month about cars with nobody driving them.
- Cadence
- Monthly. 311 posts complaints within a day; a month prints four days after it ends. Newest complete month Oct 2026. Read Nov 13, 06:40 UTC.
- Baseline
- The prior 24 months, 12 needed.
Quote this number
San Francisco took 70 complaints about driverless cars in Oct 2026, according to Tickerz, which counts them from city open data.
Asked often
- How many complaints are there about driverless cars in San Francisco?
- 70 complaints about driverless cars were made to San Francisco 311 in Oct 2026, counted by Tickerz from the city's open data.
- Where does the $ROBOCAR number come from?
- Tickerz reads it from DataSF, 311 Cases, service name Autonomous Vehicle Complaints. Monthly. 311 posts complaints within a day; a month prints four days after it ends. Each number is kept as it was first published, with a timestamped proof, and any later revision is shown beside it.
- Can I download the $ROBOCAR data?
- Yes, free and with no key: the full history as JSON at https://tickerz.com/api/indices/robocar and every period as CSV at https://tickerz.com/api/indices/robocar/history.csv.
List it
No listing kit for $ROBOCAR yet. A kit sets its strikes from 14 published numbers. This index publishes one a month and has none yet.
Resolution
- Index
- $ROBOCAR Complaints about driverless cars in San Francisco. Rulebook v0.2, 2026-10-04.
- Prints
- Monthly. 311 posts complaints within a day; a month prints four days after it ends. The newest complete month is on the record after the daily proof at 12:40 UTC.
- As first published
Oct 2026 is not timestamped yet. The daily proof at 12:40 UTC adds it.
The number as first published is final for settlement. A revision by the source is shown beside it and never replaces it.
- Fallback
- A month prints four days after it ends. If 311 posts nothing for the month, it stays open. A month 311 never posts is void.
- Precision
- Whole complaints with that service name, by requested date.
- Cost to move
- Cheap. A complaint is a phone call, an app or a web form, and the count is small.
- Grade
- display. A small count from one reporting category: a change to the 311 app can move it. Shown, not settled on.
- For a rulebook
- Settle on the number Tickerz first recorded for $ROBOCAR for the month named in the contract, published at tickerz.com/x/robocar and in GET /api/indices/robocar, timestamped daily in Bitcoin with OpenTimestamps.
As first published
None on file yet.
Embed
Theme
Size
Badge
Card
Card, iframe
<iframe src="https://tickerz.com/embed/robocar" title="$ROBOCAR on Tickerz" width="480" height="200" style="border:0;max-width:100%" loading="lazy" allow="clipboard-write"></iframe>Proof and data
- Proof
- Every reading is timestamped in Bitcoin once a day, so nobody can change it later. The newest proof covers Nov 12, in Bitcoin block 975,557.Proof fileLive feedHow it works
Name a number
Name a number you want counted. Within 48 hours it is a ticker, or you get the plain reason it cannot be built. Answers