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

Citroen C8 2.2 HDi Biturbo 170

The Citroen C8 2.2 HDi Biturbo 170 reaches 60 mph in 9.58 s (100 km/h in 10.18 s) and covers a standing quarter mile in 17.16 s, tripping the lights at 80.0 mph. It clears the first 60 ft in 2.66 s and the eighth mile in 11.02 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 C8 2.2 HDi Biturbo 170 Renault Scenic 1.4 TCe 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 C8 2.2 HDi Biturbo 170
0–60 mph9.58 s
0–100 km/h10.18 s
0–100 mph—
60 ft2.66 s
1/8 mile11.02 s
1/4 mile17.16 s
Trap speed80.0 mph

About the C8 2.2 HDi Biturbo 170

The 2008 Citroen C8 2.2 HDi Biturbo 170 is a front-drive turbodiesel MPV of 1,818 kg with 168 bhp, which works out at 92 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.66 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 9,444th quickest to 60 mph, and the 81st quickest of the 387 Citroens here. Its 80.0 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 C8 2.2 HDi Biturbo 170
Year2008
Power168 hp (125 kW)
Kerb mass1,818 kg
Power to weight92 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed122 mph (196 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Scenic 1.4 TCe 13020099.56 s17.08 s80.7 mph129 bhp
Renault Scenic 1.6 dCi 13020099.57 s17.04 s80.8 mph129 bhp
Chevrolet Orlando 1.4 Turbo 14020109.49 s17.27 s80.8 mph138 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 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 MPVs and people carriers478 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 C8 2.2 HDi Biturbo 170 0-60 time?
The Citroen C8 2.2 HDi Biturbo 170 reaches 60 mph in 9.58 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,444th quickest of the 14,946 cars in the set.
What is the Citroen C8 2.2 HDi Biturbo 170 quarter mile time?
17.16 s at 80.0 mph. It reaches the eighth mile in 11.02 s and clears the first 60 ft in 2.66 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen C8 2.2 HDi Biturbo 170 have?
168 bhp and 1,818 kg, which is 92 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 196 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen C8 2.2 HDi Biturbo 170?
Closest here on pace: Renault Scenic 1.4 TCe 130 (9.56 s), Renault Scenic 1.6 dCi 130 (9.57 s), Chevrolet Orlando 1.4 Turbo 140 (9.49 s). Each one can be raced against the Citroen C8 2.2 HDi Biturbo 170 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 C8 2.2 HDi Biturbo 170 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.