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

Ford Focus C-Max 2.0 TDCi 136

The Ford Focus C-Max 2.0 TDCi 136 reaches 60 mph in 8.24 s (100 km/h in 9.23 s) and covers a standing quarter mile in 16.46 s, tripping the lights at 83.8 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 10.60 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.

Ford Focus C-Max 2.0 TDCi 136 MINI Hatch Cooper D 1.5 116

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 Ford Focus C-Max 2.0 TDCi 136
0–60 mph8.24 s
0–100 km/h9.23 s
0–100 mph—
60 ft2.49 s
1/8 mile10.60 s
1/4 mile16.46 s
Trap speed83.8 mph

About the Focus C-Max 2.0 TDCi 136

The 2003 Ford Focus C-Max 2.0 TDCi 136 is a front-drive turbodiesel car of 1,427 kg with 134 bhp, which works out at 94 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.49 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 6,979th quickest to 60 mph, and the 224th quickest of the 789 Fords here. It leaves better than it pulls: 83.8 mph at the lights is only the 7,928th 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 Ford Focus C-Max 2.0 TDCi 136
Year2003
Power134 hp (100 kW)
Kerb mass1,427 kg
Power to weight94 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
MINI Hatch Cooper D 1.5 11620188.25 s16.42 s83.6 mph114 bhp
MINI F55 Hatch Cooper D 1.5 11620148.25 s16.42 s83.6 mph114 bhp
Mercedes-Benz A 180 (W177)20188.26 s16.40 s84.4 mph134 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Ford 0-60 timesevery modelFastest diesel cars4,019 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 Ford Focus C-Max 2.0 TDCi 136 0-60 time?
The Ford Focus C-Max 2.0 TDCi 136 reaches 60 mph in 8.24 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,979th quickest of the 14,946 cars in the set.
What is the Ford Focus C-Max 2.0 TDCi 136 quarter mile time?
16.46 s at 83.8 mph. It reaches the eighth mile in 10.60 s and clears the first 60 ft in 2.49 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ford Focus C-Max 2.0 TDCi 136 have?
134 bhp and 1,427 kg, which is 94 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford Focus C-Max 2.0 TDCi 136?
Closest here on pace: MINI Hatch Cooper D 1.5 116 (8.25 s), MINI F55 Hatch Cooper D 1.5 116 (8.25 s), Mercedes-Benz A 180 (W177) (8.26 s). Each one can be raced against the Ford Focus C-Max 2.0 TDCi 136 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 Ford Focus C-Max 2.0 TDCi 136 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.