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

MINI Clubman JCW Mk I

The MINI Clubman JCW Mk I reaches 60 mph in 6.09 s (100 km/h in 6.43 s) and covers a standing quarter mile in 14.66 s, tripping the lights at 94.8 mph. It clears the first 60 ft in 2.29 s and the eighth mile in 9.44 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 Clubman JCW Mk I Cadillac CTS 4 2.0T

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 Clubman JCW Mk I
0–60 mph6.09 s
0–100 km/h6.43 s
0–100 mph—
60 ft2.29 s
1/8 mile9.44 s
1/4 mile14.66 s
Trap speed94.8 mph

About the Clubman JCW Mk I

The 2008 MINI Clubman JCW Mk I is a front-drive turbocharged car of 1,263 kg with 208 bhp, which works out at 165 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.29 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,352nd quickest to 60 mph, inside the fastest quarter, and the 10th quickest of the 122 MINIs here. Its 94.8 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.

On paper

Specification MINI Clubman JCW Mk I
Year2008
Power208 hp (155 kW)
Kerb mass1,263 kg
Power to weight165 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed149 mph (239 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Cadillac CTS 4 2.0T20156.04 s14.59 s94.3 mph272 bhp
Abarth 500 / 595 / 695 595/695 Competizione 1.4 T-Jet 18020156.07 s14.55 s100.3 mph177 bhp
Ford Fiesta ST (Mk8)20196.14 s14.58 s96.2 mph197 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.

Head to head

BMW M135i F20 vs MINI Clubman JCW Mk IFull comparison

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 hatchbacks4,513 carsFastest cars of the 2000s5,138 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 Clubman JCW Mk I 0-60 time?
The MINI Clubman JCW Mk I reaches 60 mph in 6.09 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,352nd quickest of the 14,946 cars in the set.
What is the MINI Clubman JCW Mk I quarter mile time?
14.66 s at 94.8 mph. It reaches the eighth mile in 9.44 s and clears the first 60 ft in 2.29 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the MINI Clubman JCW Mk I have?
208 bhp and 1,263 kg, which is 165 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 239 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the MINI Clubman JCW Mk I?
Closest here on pace: Cadillac CTS 4 2.0T (6.04 s), Abarth 500 / 595 / 695 595/695 Competizione 1.4 T-Jet 180 (6.07 s), Ford Fiesta ST (Mk8) (6.14 s). Each one can be raced against the MINI Clubman JCW Mk I 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 Clubman JCW Mk I is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 10 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.