← My Auto Racer All cars Citroen 0-60 Comparisons Answers
The Citroen C2 VTS reaches 60 mph in 8.25 s and covers a standing quarter mile in 16.52 s, tripping the lights at 84.0 mph. It clears the first 60 ft in 2.57 s and the eighth mile in 10.67 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Citroen C2 VTS |
|---|---|
| 0–60 mph | 8.25 s |
| 0–100 mph | — |
| 60 ft | 2.57 s |
| 1/8 mile | 10.67 s |
| 1/4 mile | 16.52 s |
| Trap speed | 84.0 mph |
The 2004 Citroen C2 VTS is a front-drive naturally aspirated car of 1,105 kg with 123 bhp, which works out at 112 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.57 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,683rd quickest to 60 mph, and the 10th quickest of the 15 Citroens here. Its 84.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 9 of 9 published acceleration figures for this car.
| Specification | Citroen C2 VTS |
|---|---|
| Year | 2004 |
| Power | 123 bhp |
| Kerb mass | 1,105 kg |
| Power to weight | 112 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 199 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lancia Delta 1.4 T-Jet 16V | 2008 | 8.32 s | 16.53 s | 85.4 mph | 148 bhp |
| Renault Megane Sport 2.0 dCi | 2007 | 8.33 s | 16.52 s | 86.9 mph | 170 bhp |
| Rover 827i Fastback | 1988 | 8.24 s | 16.48 s | 88.9 mph | 177 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.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.