# Serve Robotics safety record 8 incident(s) on file for Serve Robotics, rolled up across its models and deployments (operated or manufactured). Retracted claims are excluded from this count but remain reachable at their own canonical URLs. [Back to Serve Robotics](/companies/serve-robotics.md) ## Incidents (8) - [Georgia HB 986 takes effect July 1, 2026 - delivery robot sidewalk speed raised to 7 mph](/incidents/regulatory-action-2026-07-01-serve-robotics.md) (2026-07-01): Regulatory action · severity: minor · other · other - [New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury](/incidents/injury-2026-05-11-serve-robotics.md) (2026-05-11): Injury · severity: serious · none - [Serve Robotics delivery robot crashes into Chicago bus shelter shattering glass](/incidents/property-damage-2026-03-24-serve-robotics.md) (2026-03-24): Property damage · severity: minor - [Serve Robotics delivery robot crashed through glass CTA bus shelter in Chicago West Town](/incidents/property-damage-2026-03-22-serve-robotics.md) (2026-03-22): Property damage · severity: minor · none - [Serve Robotics delivery robot 'Nasir' shattered a CTA bus shelter in Chicago's West Town](/incidents/serve-chicago-bus-shelter-2026-03-22.md) (2026-03-22): Property damage · severity: minor - [Serve Robotics delivery robot crashes through CTA bus shelter in Chicago](/incidents/property-damage-2026-03-15-serve-robotics.md) (2026-03-15): Property damage · severity: minor · none - [Serve Robotics delivery robot collides with man with cerebral palsy on mobility scooter in West Hollywood](/incidents/collision-2025-09-25-serve-robotics.md) (2025-09-25): Collision · severity: minor · none - [Serve Robotics delivery robot and mobility-scooter user involved in sidewalk encounter, West Hollywood (Sept 2025)](/incidents/serve-weho-mobility-scooter-collision-2025-09-12.md) (2025-09-12): Other · severity: minor ## Exposure DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for Serve Robotics's 4 recorded deployment(s). No incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators; there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today. ## A note on NHTSA's crash-reporting data Many of the incidents below are drawn from NHTSA's Standing General Order (SGO) 2021-01 crash-reporting program, which requires manufacturers and operators of automated driving systems (ADS) and advanced driver-assistance systems (ADAS) to report qualifying crashes. It is the only nationwide, cross-operator crash dataset that exists for this industry, and it is also, by NHTSA's own design and Consumer Reports' public assessment, an imperfect one. Reporting companies may redact narrative fields as confidential business information (CBI). In practice this means narrative completeness is uneven across manufacturers in the underlying dataset: some incident reports read as full prose descriptions of what happened, others are replaced with boilerplate redacted text. This is a property of the source data, not of DEPLOY's editorial process; DEPLOY publishes what the filing discloses and states plainly when a fuller account is not publicly available. The SGO dataset also does not publish exposure denominators (miles driven, hours operated, rides given) alongside crash counts, so a raw incident count cannot be turned into a rate without an independently sourced denominator. See "Exposure" below for what DEPLOY does and does not have on file for this company. - [NHTSA: Standing General Order on Crash Reporting](https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting) - [Consumer Reports: comments to NHTSA on incident reporting for ADS and Level 2 ADAS](https://advocacy.consumerreports.org/research/consumer-reports-comments-to-nhtsa-on-incident-reporting-for-automated-driving-systems-and-level-2-adas/) - [Consumer Reports: statement on crash-reporting underreporting](https://advocacy.consumerreports.org/press_release/transportation-department-keeps-in-place-vital-car-crash-reporting-program-but-misses-chance-to-address-underreporting-consumer-reports-statement/) ## Common questions **What is Serve Robotics's safety record?** DEPLOY has 8 incidents on file for Serve Robotics, drawn from NHTSA's Standing General Order crash-reporting program and press coverage. Each incident below is individually sourced and dated; see the incident list for details. **Is Serve Robotics safer than a human driver?** DEPLOY does not have exposure data (miles driven or hours operated) on file for Serve Robotics, so no per-mile or per-hour safety rate can be computed from this registry today. This is a documented industry-wide data gap, not unique to DEPLOY: NHTSA's own SGO dataset does not publish exposure denominators alongside crash counts. Any rate comparison you see elsewhere may rely on a company's self-published mileage figures, which are not independently audited. **Does DEPLOY redact or omit crash details for Serve Robotics?** No. DEPLOY does not redact incident narratives. Where a source narrative is itself incomplete (for example, a NHTSA SGO filing redacted as confidential business information), DEPLOY states that plainly rather than filling the gap. See "A note on NHTSA's crash-reporting data" below. _API: GET /v1/safety/companies/fe7b5d4c-4e52-4f57-8593-b8289761539b/profile (bearer-gated) · canonical URL: /companies/serve-robotics/safety-record_