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

Citroen C-Elysee 1.6 VTi 115

The Citroen C-Elysee 1.6 VTi 115 reaches 60 mph in 9.90 s (100 km/h in 10.42 s) and covers a standing quarter mile in 17.76 s, tripping the lights at 83.0 mph. It clears the first 60 ft in 3.15 s and the eighth mile in 11.80 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 C-Elysee 1.6 VTi 115 Lancia Ypsilon 1.4 95 (2006)

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 C-Elysee 1.6 VTi 115
0–60 mph9.90 s
0–100 km/h10.42 s
0–100 mph—
60 ft3.15 s
1/8 mile11.80 s
1/4 mile17.76 s
Trap speed83.0 mph

About the C-Elysee 1.6 VTi 115

The 2013 Citroen C-Elysee 1.6 VTi 115 is a front-drive naturally aspirated car of 1,165 kg with 114 bhp, which works out at 98 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.15 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,945th quickest to 60 mph, and the 97th quickest of the 387 Citroens here. It traps higher than its 0-60 suggests — 83.0 mph, the 8,371st highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Citroen C-Elysee 1.6 VTi 115
Year2013
Power114 hp (85 kW)
Kerb mass1,165 kg
Power to weight98 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed117 mph (188 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Ypsilon 1.4 95 (2006)20069.87 s17.61 s79.4 mph94 bhp
Mitsubishi Colt CZ3 1.3 9520049.95 s17.71 s77.6 mph94 bhp
Lancia Ypsilon 1.4 95 (2003)20039.91 s17.59 s79.4 mph94 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 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 C-Elysee 1.6 VTi 115 0-60 time?
The Citroen C-Elysee 1.6 VTi 115 reaches 60 mph in 9.90 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,945th quickest of the 14,946 cars in the set.
What is the Citroen C-Elysee 1.6 VTi 115 quarter mile time?
17.76 s at 83.0 mph. It reaches the eighth mile in 11.80 s and clears the first 60 ft in 3.15 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen C-Elysee 1.6 VTi 115 have?
114 bhp and 1,165 kg, which is 98 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 188 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen C-Elysee 1.6 VTi 115?
Closest here on pace: Lancia Ypsilon 1.4 95 (2006) (9.87 s), Mitsubishi Colt CZ3 1.3 95 (9.95 s), Lancia Ypsilon 1.4 95 (2003) (9.91 s). Each one can be raced against the Citroen C-Elysee 1.6 VTi 115 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 C-Elysee 1.6 VTi 115 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.