← My Auto Racer All cars Citroen 0-60 Comparisons
The Citroen DS3 Performance reaches 60 mph in 5.69 s and covers a standing quarter mile in 14.29 s, tripping the lights at 97.6 mph. It clears the first 60 ft in 2.28 s and the eighth mile in 9.25 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 DS3 Performance |
|---|---|
| 0–60 mph | 5.69 s |
| 0–100 mph | — |
| 60 ft | 2.28 s |
| 1/8 mile | 9.25 s |
| 1/4 mile | 14.29 s |
| Trap speed | 97.6 mph |
The 2016 Citroen DS3 Performance is a front-drive turbocharged car of 1,202 kg with 205 bhp, which works out at 171 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.28 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 1,789th quickest to 60 mph, and the quickest of the 15 Citroens here. Its 97.6 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.
| Specification | Citroen DS3 Performance |
|---|---|
| Year | 2016 |
| Power | 205 bhp |
| Kerb mass | 1,202 kg |
| Power to weight | 171 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 232 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Hyundai i20 N BC3 | 2021 | 5.66 s | 14.30 s | 96.8 mph | 201 bhp |
| Acura TSX V-6 | 2010 | 5.71 s | 14.34 s | 97.8 mph | 280 bhp |
| Honda Accord 2.0T Mk X | 2018 | 5.72 s | 14.32 s | 99.5 mph | 252 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-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.