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

Citroen Saxo VTR 1.6i

The Citroen Saxo VTR 1.6i reaches 60 mph in 8.62 s (100 km/h in 9.10 s) and covers a standing quarter mile in 16.63 s, tripping the lights at 84.7 mph. It clears the first 60 ft in 2.74 s and the eighth mile in 10.78 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 Saxo VTR 1.6i Vauxhall Insignia Hatchback 2.0 CDTI ecoFLEX ( 160 HP)

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 Saxo VTR 1.6i
0–60 mph8.62 s
0–100 km/h9.10 s
0–100 mph—
60 ft2.74 s
1/8 mile10.78 s
1/4 mile16.63 s
Trap speed84.7 mph

About the Saxo VTR 1.6i

The 1997 Citroen Saxo VTR 1.6i is a front-drive naturally aspirated car of 920 kg with 89 bhp, which works out at 96 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.74 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 7,737th quickest to 60 mph, and the 51st quickest of the 387 Citroens here. Its 84.7 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 1 of 1 published acceleration figures for this car.

On paper

Specification Citroen Saxo VTR 1.6i
Year1997
Power89 hp (66 kW)
Kerb mass920 kg
Power to weight96 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Vauxhall Insignia Hatchback 2.0 CDTI ecoFLEX ( 160 HP)20088.60 s16.61 s84.5 mph158 bhp
Opel Astra 5dr 1.4 ECOTEC Start/Stop 12520158.57 s16.65 s82.4 mph123 bhp
Renault Mégane Hatch 1.9 dCi 13020088.57 s16.65 s82.9 mph129 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 cars0-100 km/h under 10 seconds9,062 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 1990s2,649 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 Saxo VTR 1.6i 0-60 time?
The Citroen Saxo VTR 1.6i reaches 60 mph in 8.62 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,737th quickest of the 14,946 cars in the set.
What is the Citroen Saxo VTR 1.6i quarter mile time?
16.63 s at 84.7 mph. It reaches the eighth mile in 10.78 s and clears the first 60 ft in 2.74 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen Saxo VTR 1.6i have?
89 bhp and 920 kg, which is 96 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen Saxo VTR 1.6i?
Closest here on pace: Vauxhall Insignia Hatchback 2.0 CDTI ecoFLEX ( 160 HP) (8.60 s), Opel Astra 5dr 1.4 ECOTEC Start/Stop 125 (8.57 s), Renault Mégane Hatch 1.9 dCi 130 (8.57 s). Each one can be raced against the Citroen Saxo VTR 1.6i 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 Saxo VTR 1.6i is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 1 of its 1 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.