← My Auto Racer All cars MINI 0-60 Comparisons Answers

MINI F55 Hatch Cooper SD 2.0 170

The MINI F55 Hatch Cooper SD 2.0 170 reaches 60 mph in 6.49 s (100 km/h in 6.84 s) and covers a standing quarter mile in 15.00 s, tripping the lights at 94.4 mph. It clears the first 60 ft in 2.46 s and the eighth mile in 9.78 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.

MINI F55 Hatch Cooper SD 2.0 170 Infiniti Q30 2.0 t 211

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start MINI F55 Hatch Cooper SD 2.0 170
0–60 mph6.49 s
0–100 km/h6.84 s
0–100 mph—
60 ft2.46 s
1/8 mile9.78 s
1/4 mile15.00 s
Trap speed94.4 mph

About the F55 Hatch Cooper SD 2.0 170

The 2014 MINI F55 Hatch Cooper SD 2.0 170 is a front-drive turbodiesel car of 1,195 kg with 168 bhp, which works out at 140 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.46 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 3,863rd quickest to 60 mph, and the 23rd quickest of the 122 MINIs here. Its 94.4 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 2 of 2 published acceleration figures for this car.

On paper

Specification MINI F55 Hatch Cooper SD 2.0 170
Year2014
Power168 hp (125 kW)
Kerb mass1,195 kg
Power to weight140 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed140 mph (225 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Infiniti Q30 2.0 t 21120156.49 s14.96 s95.2 mph208 bhp
Alpina D3 Biturbo20086.45 s14.91 s95.2 mph211 bhp
Mercedes-Benz B-Class (W247) B 220d 19020196.49 s14.97 s95.1 mph188 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.

Where these times sit

0-60 under 7 seconds4,651 cars0-100 km/h under 7 seconds4,031 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
MINI 0-60 timesevery modelFastest small cars1,681 carsFastest cars of the 2010s4,541 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the MINI F55 Hatch Cooper SD 2.0 170 0-60 time?
The MINI F55 Hatch Cooper SD 2.0 170 reaches 60 mph in 6.49 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,863rd quickest of the 14,946 cars in the set.
What is the MINI F55 Hatch Cooper SD 2.0 170 quarter mile time?
15.00 s at 94.4 mph. It reaches the eighth mile in 9.78 s and clears the first 60 ft in 2.46 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the MINI F55 Hatch Cooper SD 2.0 170 have?
168 bhp and 1,195 kg, which is 140 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 225 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the MINI F55 Hatch Cooper SD 2.0 170?
Closest here on pace: Infiniti Q30 2.0 t 211 (6.49 s), Alpina D3 Biturbo (6.45 s), Mercedes-Benz B-Class (W247) B 220d 190 (6.49 s). Each one can be raced against the MINI F55 Hatch Cooper SD 2.0 170 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The MINI F55 Hatch Cooper SD 2.0 170 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.