← My Auto Racer All cars Mazda 0-60 Comparisons
The Mazda 3 MPS reaches 60 mph in 5.55 s and covers a standing quarter mile in 14.10 s, tripping the lights at 99.1 mph. It clears the first 60 ft in 2.22 s and the eighth mile in 9.10 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 3 MPS |
|---|---|
| 0–60 mph | 5.55 s |
| 0–100 mph | — |
| 60 ft | 2.22 s |
| 1/8 mile | 9.10 s |
| 1/4 mile | 14.10 s |
| Trap speed | 99.1 mph |
The 2006 Mazda 3 MPS is a front-drive turbocharged car of 1,485 kg with 256 bhp, which works out at 172 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.22 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 1,704th quickest to 60 mph, and the 3rd quickest of the 30 Mazdas here. Its 99.1 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 10 published acceleration figures for this car.
| Specification | Mazda 3 MPS |
|---|---|
| Year | 2006 |
| Power | 256 bhp |
| Kerb mass | 1,485 kg |
| Power to weight | 172 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Peugeot 208 GTi Peugeot Sport | 2015 | 5.51 s | 14.14 s | 98.2 mph | 205 bhp |
| Renault Megane RS Mk III | 2009 | 5.53 s | 14.00 s | 101.5 mph | 247 bhp |
| Skoda Octavia Combi RS 245 Mk III facelift | 2017 | 5.67 s | 14.11 s | 101.4 mph | 241 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.