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

Citroen DS4 THP 200

The Citroen DS4 THP 200 reaches 60 mph in 6.58 s (100 km/h in 6.95 s) and covers a standing quarter mile in 15.09 s, tripping the lights at 93.3 mph. It clears the first 60 ft in 2.43 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.

Citroen DS4 THP 200 Abarth 500 / 595 / 695 595 Turismo 1.4 T-Jet 165

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 DS4 THP 200
0–60 mph6.58 s
0–100 km/h6.95 s
0–100 mph—
60 ft2.43 s
1/8 mile9.78 s
1/4 mile15.09 s
Trap speed93.3 mph

About the DS4 THP 200

The 2012 Citroen DS4 THP 200 is a front-drive turbocharged car of 1,250 kg with 197 bhp, which works out at 158 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.43 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,985th quickest to 60 mph, and the 4th quickest of the 387 Citroens here. Its 93.3 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 Citroen DS4 THP 200
Year2012
Power197 hp (147 kW)
Kerb mass1,250 kg
Power to weight158 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed146 mph (235 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Abarth 500 / 595 / 695 595 Turismo 1.4 T-Jet 16520126.57 s15.19 s93.1 mph162 bhp
Renault Clio 19720066.65 s15.21 s92.0 mph194 bhp
Fiat 595 Abarth 1.4 turismo 16520166.63 s15.23 s92.5 mph162 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

Citroen C4 Coupe 1.4 88 vs Citroen DS4 THP 200Full 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
Citroen 0-60 timesevery modelFastest hatchbacks4,513 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 Citroen DS4 THP 200 0-60 time?
The Citroen DS4 THP 200 reaches 60 mph in 6.58 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,985th quickest of the 14,946 cars in the set.
What is the Citroen DS4 THP 200 quarter mile time?
15.09 s at 93.3 mph. It reaches the eighth mile in 9.78 s and clears the first 60 ft in 2.43 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen DS4 THP 200 have?
197 bhp and 1,250 kg, which is 158 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 235 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen DS4 THP 200?
Closest here on pace: Abarth 500 / 595 / 695 595 Turismo 1.4 T-Jet 165 (6.57 s), Renault Clio 197 (6.65 s), Fiat 595 Abarth 1.4 turismo 165 (6.63 s). Each one can be raced against the Citroen DS4 THP 200 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 DS4 THP 200 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.