← My Auto Racer All cars Acura 0-60 Comparisons
The Acura ZDX reaches 60 mph in 6.40 s and covers a standing quarter mile in 14.93 s, tripping the lights at 93.2 mph. It clears the first 60 ft in 2.40 s and the eighth mile in 9.64 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 | Acura ZDX |
|---|---|
| 0–60 mph | 6.40 s |
| 0–100 mph | — |
| 60 ft | 2.40 s |
| 1/8 mile | 9.64 s |
| 1/4 mile | 14.93 s |
| Trap speed | 93.2 mph |
The 2010 Acura ZDX is an all-wheel-drive naturally aspirated SUV of 2,020 kg with 300 bhp, which works out at 149 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.40 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 2,929 cars in the set it is the 2,146th quickest to 60 mph, and the 3rd quickest of the 5 Acuras here. Its 93.2 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 | Acura ZDX |
|---|---|
| Year | 2010 |
| Power | 300 bhp |
| Kerb mass | 2,020 kg |
| Power to weight | 149 bhp/t |
| Drivetrain | All-wheel drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 230 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Kia Ceed GT 1.6T GDI Mk II | 2013 | 6.37 s | 14.89 s | 94.4 mph | 201 bhp |
| Kia Pro Ceed GT Mk II | 2013 | 6.40 s | 14.95 s | 93.4 mph | 201 bhp |
| Subaru BRZ | 2012 | 6.39 s | 14.94 s | 93.4 mph | 197 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-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.