← My Auto Racer All cars MINI 0-60 Comparisons
The MINI Coupé John Cooper Works reaches 60 mph in 5.86 s and covers a standing quarter mile in 14.35 s, tripping the lights at 98.7 mph. It clears the first 60 ft in 2.36 s and the eighth mile in 9.37 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 | MINI Coupé John Cooper Works |
|---|---|
| 0–60 mph | 5.86 s |
| 0–100 mph | — |
| 60 ft | 2.36 s |
| 1/8 mile | 9.37 s |
| 1/4 mile | 14.35 s |
| Trap speed | 98.7 mph |
The 2011 MINI Coupé John Cooper Works is a front-drive turbocharged roadster of 1,230 kg with 208 bhp, which works out at 169 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.36 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,888th quickest to 60 mph, and the 5th quickest of the 23 MINIs here. Its 98.7 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 | MINI Coupé John Cooper Works |
|---|---|
| Year | 2011 |
| Power | 208 bhp |
| Kerb mass | 1,230 kg |
| Power to weight | 169 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 240 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mazda MX-5 2.0 (ND2) | 2019 | 6.00 s | 14.49 s | 95.1 mph | 181 bhp |
| Ford Focus ST | 2012 | 5.84 s | 14.36 s | 98.2 mph | 247 bhp |
| SEAT Leon Cupra | 2006 | 5.82 s | 14.36 s | 97.5 mph | 237 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.