← My Auto Racer All cars Honda 0-60 Comparisons Answers
The Honda CR-Z reaches 60 mph in 9.00 s and covers a standing quarter mile in 17.03 s, tripping the lights at 82.0 mph. It clears the first 60 ft in 2.78 s and the eighth mile in 11.02 s.
Simulated, not measured — computed from published kerb mass, rated power, gearing and drivetrain, then fitted to this car’s own published acceleration figures. Dry asphalt, 20 °C, sea level, 1 ft rollout.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Honda CR-Z |
|---|---|
| 0–60 mph | 9.00 s |
| 0–100 mph | — |
| 60 ft | 2.78 s |
| 1/8 mile | 11.02 s |
| 1/4 mile | 17.03 s |
| Trap speed | 82.0 mph |
The 2010 Honda CR-Z is a front-drive naturally aspirated car of 1,198 kg with 122 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.78 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,801st quickest to 60 mph, and the 32nd quickest of the 40 Hondas here. Its 82.0 mph trap speed sits about where its 0-60 puts it, so it launches and pulls in roughly equal measure. The simulation is trimmed to 9 of 9 published acceleration figures for this car.
| Specification | Honda CR-Z |
|---|---|
| Year | 2010 |
| Power | 122 bhp |
| Kerb mass | 1,198 kg |
| Power to weight | 102 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 200 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| MG Montego EFi | 1984 | 9.09 s | 16.96 s | 84.8 mph | 117 bhp |
| Nissan Bluebird 1.8 ZX Turbo Pre-Facelift T12 | 1986 | 8.94 s | 16.80 s | 86.5 mph | 133 bhp |
| Subaru XT Turbo | 1985 | 8.97 s | 16.83 s | 84.1 mph | 134 bhp |
Picked for a fair race, not just a matching 0-60: pace, power-to-weight and body shape all count, and at most one is from the same maker.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.