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

MINI Paceman Cooper D 1.6D 112

The MINI Paceman Cooper D 1.6D 112 reaches 60 mph in 10.09 s (100 km/h in 10.77 s) and covers a standing quarter mile in 17.51 s, tripping the lights at 77.7 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 11.18 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 Paceman Cooper D 1.6D 112 Mazda CX-30 2.0 SKYACTIVE 122

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 Paceman Cooper D 1.6D 112
0–60 mph10.09 s
0–100 km/h10.77 s
0–100 mph—
60 ft2.64 s
1/8 mile11.18 s
1/4 mile17.51 s
Trap speed77.7 mph

About the Paceman Cooper D 1.6D 112

The 2013 MINI Paceman Cooper D 1.6D 112 is a front-drive turbodiesel car of 1,320 kg with 110 bhp, which works out at 83 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.64 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 10,313th quickest to 60 mph, and the 99th quickest of the 122 MINIs here. It leaves better than it pulls: 77.7 mph at the lights is only the 11,285th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification MINI Paceman Cooper D 1.6D 112
Year2013
Power110 hp (82 kW)
Kerb mass1,320 kg
Power to weight83 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed113 mph (182 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda CX-30 2.0 SKYACTIVE 122201910.11 s17.59 s78.8 mph121 bhp
Citroen C4 Hatchback 1.6 HDi 110200810.16 s17.55 s78.5 mph107 bhp
Nissan Note 1.5 dCI 106200810.08 s17.46 s78.4 mph105 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
MINI 0-60 timesevery modelFastest diesel cars4,019 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 Paceman Cooper D 1.6D 112 0-60 time?
The MINI Paceman Cooper D 1.6D 112 reaches 60 mph in 10.09 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,313th quickest of the 14,946 cars in the set.
What is the MINI Paceman Cooper D 1.6D 112 quarter mile time?
17.51 s at 77.7 mph. It reaches the eighth mile in 11.18 s and clears the first 60 ft in 2.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the MINI Paceman Cooper D 1.6D 112 have?
110 bhp and 1,320 kg, which is 83 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 182 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the MINI Paceman Cooper D 1.6D 112?
Closest here on pace: Mazda CX-30 2.0 SKYACTIVE 122 (10.11 s), Citroen C4 Hatchback 1.6 HDi 110 (10.16 s), Nissan Note 1.5 dCI 106 (10.08 s). Each one can be raced against the MINI Paceman Cooper D 1.6D 112 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 Paceman Cooper D 1.6D 112 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.