← My Auto Racer All cars Mazda 0-60 Comparisons
The Mazda MX-5 2.0 (ND2) reaches 60 mph in 6.00 s and covers a standing quarter mile in 14.49 s, tripping the lights at 95.1 mph. It clears the first 60 ft in 2.22 s and the eighth mile in 9.34 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 | Mazda MX-5 2.0 (ND2) |
|---|---|
| 0–60 mph | 6.00 s |
| 0–100 mph | — |
| 60 ft | 2.22 s |
| 1/8 mile | 9.34 s |
| 1/4 mile | 14.49 s |
| Trap speed | 95.1 mph |
The 2019 Mazda MX-5 2.0 (ND2) is a rear-drive naturally aspirated roadster of 1,045 kg with 181 bhp, which works out at 173 bhp per tonne. Rear drive and 173 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.22 s. Against the 2,929 cars in the set it is the 1,949th quickest to 60 mph, and the 8th quickest of the 30 Mazdas here. It leaves better than it pulls: 95.1 mph at the lights is only the 2,132nd highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Mazda MX-5 2.0 (ND2) |
|---|---|
| Year | 2019 |
| Power | 181 bhp |
| Kerb mass | 1,045 kg |
| Power to weight | 173 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 233 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| MINI Roadster JCW | 2012 | 6.06 s | 14.64 s | 95.1 mph | 208 bhp |
| MINI Coupé John Cooper Works | 2011 | 5.86 s | 14.35 s | 98.7 mph | 208 bhp |
| BMW Z4 20i G29 | 2019 | 5.92 s | 14.49 s | 95.5 mph | 194 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.