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

Citroen C4 Hatchback 2.0 136

The Citroen C4 Hatchback 2.0 136 reaches 60 mph in 8.37 s (100 km/h in 8.84 s) and covers a standing quarter mile in 16.36 s, tripping the lights at 86.7 mph. It clears the first 60 ft in 2.79 s and the eighth mile in 10.69 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.

Citroen C4 Hatchback 2.0 136 Ford Focus 3dr 2.0 130

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 Citroen C4 Hatchback 2.0 136
0–60 mph8.37 s
0–100 km/h8.84 s
0–100 mph—
60 ft2.79 s
1/8 mile10.69 s
1/4 mile16.36 s
Trap speed86.7 mph

About the C4 Hatchback 2.0 136

The 2004 Citroen C4 Hatchback 2.0 136 is a front-drive naturally aspirated car of 1,262 kg with 134 bhp, which works out at 106 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.79 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 7,248th quickest to 60 mph, and the 40th quickest of the 387 Citroens here. Its 86.7 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 Citroen C4 Hatchback 2.0 136
Year2004
Power134 hp (100 kW)
Kerb mass1,262 kg
Power to weight106 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed129 mph (207 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ford Focus 3dr 2.0 13020018.37 s16.39 s86.3 mph129 bhp
MINI Hatch Cooper 1.6 11620018.37 s16.39 s86.2 mph114 bhp
Ford Focus 5dr 2.0 14820048.37 s16.37 s86.7 mph146 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
Citroen 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 Citroen C4 Hatchback 2.0 136 0-60 time?
The Citroen C4 Hatchback 2.0 136 reaches 60 mph in 8.37 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,248th quickest of the 14,946 cars in the set.
What is the Citroen C4 Hatchback 2.0 136 quarter mile time?
16.36 s at 86.7 mph. It reaches the eighth mile in 10.69 s and clears the first 60 ft in 2.79 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen C4 Hatchback 2.0 136 have?
134 bhp and 1,262 kg, which is 106 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 207 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen C4 Hatchback 2.0 136?
Closest here on pace: Ford Focus 3dr 2.0 130 (8.37 s), MINI Hatch Cooper 1.6 116 (8.37 s), Ford Focus 5dr 2.0 148 (8.37 s). Each one can be raced against the Citroen C4 Hatchback 2.0 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 Citroen C4 Hatchback 2.0 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.