← My Auto Racer All cars MINI 0-60 Comparisons Answers
The MINI Cooper reaches 60 mph in 8.49 s and covers a standing quarter mile in 16.66 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.69 s and the eighth mile in 10.75 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 Cooper |
|---|---|
| 0–60 mph | 8.49 s |
| 0–100 mph | — |
| 60 ft | 2.69 s |
| 1/8 mile | 10.75 s |
| 1/4 mile | 16.66 s |
| Trap speed | 83.2 mph |
The 2006 MINI Cooper is a front-drive naturally aspirated car of 1,040 kg with 118 bhp, which works out at 113 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.69 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,732nd quickest to 60 mph, and the 23rd quickest of the 23 MINIs here. Its 83.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 | MINI Cooper |
|---|---|
| Year | 2006 |
| Power | 118 bhp |
| Kerb mass | 1,040 kg |
| Power to weight | 113 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 203 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Saab 9-3 1.9 TTiD 180 SportCombi Mk II | 2007 | 8.48 s | 16.63 s | 86.6 mph | 177 bhp |
| MINI Cooper D | 2010 | 8.41 s | 16.58 s | 82.9 mph | 110 bhp |
| Renault Megane TCe 140 (Mk4) | 2018 | 8.49 s | 16.60 s | 82.9 mph | 138 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.