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

Citroen C1 5dr 1.2 PureTech 82

The Citroen C1 5dr 1.2 PureTech 82 reaches 60 mph in 9.92 s (100 km/h in 10.59 s) and covers a standing quarter mile in 17.52 s, tripping the lights at 77.9 mph. It clears the first 60 ft in 2.68 s and the eighth mile in 11.18 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 C1 5dr 1.2 PureTech 82 Chevrolet Classic 1.8 102

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 C1 5dr 1.2 PureTech 82
0–60 mph9.92 s
0–100 km/h10.59 s
0–100 mph—
60 ft2.68 s
1/8 mile11.18 s
1/4 mile17.52 s
Trap speed77.9 mph

About the C1 5dr 1.2 PureTech 82

The 2014 Citroen C1 5dr 1.2 PureTech 82 is a front-drive turbocharged car of 865 kg with 80 bhp, which works out at 93 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.68 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,998th quickest to 60 mph, and the 98th quickest of the 387 Citroens here. It leaves better than it pulls: 77.9 mph at the lights is only the 11,184th 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 Citroen C1 5dr 1.2 PureTech 82
Year2014
Power80 hp (60 kW)
Kerb mass865 kg
Power to weight93 bhp/t
DrivetrainFront drive
Gears5
EngineTurbocharged
Top speed106 mph (171 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Classic 1.8 10220029.92 s17.57 s79.8 mph101 bhp
SEAT Toledo 1.6 16V 10519999.94 s17.52 s80.9 mph103 bhp
Proton Iriz 1.6 CVT 10920149.96 s17.56 s77.3 mph107 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 small cars1,681 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 C1 5dr 1.2 PureTech 82 0-60 time?
The Citroen C1 5dr 1.2 PureTech 82 reaches 60 mph in 9.92 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,998th quickest of the 14,946 cars in the set.
What is the Citroen C1 5dr 1.2 PureTech 82 quarter mile time?
17.52 s at 77.9 mph. It reaches the eighth mile in 11.18 s and clears the first 60 ft in 2.68 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen C1 5dr 1.2 PureTech 82 have?
80 bhp and 865 kg, which is 93 bhp per tonne. It is front-drive, turbocharged, with 5 gears and a quoted top speed of 171 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen C1 5dr 1.2 PureTech 82?
Closest here on pace: Chevrolet Classic 1.8 102 (9.92 s), SEAT Toledo 1.6 16V 105 (9.94 s), Proton Iriz 1.6 CVT 109 (9.96 s). Each one can be raced against the Citroen C1 5dr 1.2 PureTech 82 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 C1 5dr 1.2 PureTech 82 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.