# RoboParty safety record

DEPLOY has no incidents on file for RoboParty. This rolls up incidents attached directly to RoboParty, to its models, and to its deployments (operated or manufactured).

[Back to RoboParty](/companies/roboparty.md)

## Incidents (0)

_No incidents on record. Absence of a recorded incident is not proof of a clean operating history._

## Exposure

DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for RoboParty. 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.

## Common questions

**What is RoboParty's safety record?**

DEPLOY has no incidents on file for RoboParty. This reflects the incidents DEPLOY has tracked and verified to date, drawn primarily from NHTSA's [Standing General Order](/regulations/nhtsa-sgo-2021-01-third-amended-2025.md) crash-reporting program and press coverage; it is not a safety guarantee, and absence of a recorded incident is not proof of a clean operating history.

**Is RoboParty safer than a human driver?**

DEPLOY does not have exposure data (miles driven or hours operated) on file for RoboParty, 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](/regulations/nhtsa-sgo-2021-01-third-amended-2025.md) 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 RoboParty?**

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/2151483f-0a40-49a2-89ce-dfc9c720519d/profile (bearer-gated) · canonical URL: /companies/roboparty/safety-record_