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

Chevrolet Cruze 1.7 VCDi 132

The Chevrolet Cruze 1.7 VCDi 132 reaches 60 mph in 8.90 s (100 km/h in 9.41 s) and covers a standing quarter mile in 16.69 s, tripping the lights at 82.7 mph. It clears the first 60 ft in 2.66 s and the eighth mile in 10.74 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.

Chevrolet Cruze 1.7 VCDi 132 Jaguar X-Type 2.0D 130

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 Chevrolet Cruze 1.7 VCDi 132
0–60 mph8.90 s
0–100 km/h9.41 s
0–100 mph—
60 ft2.66 s
1/8 mile10.74 s
1/4 mile16.69 s
Trap speed82.7 mph

About the Cruze 1.7 VCDi 132

The 2009 Chevrolet Cruze 1.7 VCDi 132 is a front-drive turbodiesel saloon of 1,502 kg with 129 bhp, which works out at 86 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.66 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 8,225th quickest to 60 mph, and the 114th quickest of the 199 Chevrolets here. Its 82.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 2 of 2 published acceleration figures for this car.

On paper

Specification Chevrolet Cruze 1.7 VCDi 132
Year2009
Power129 hp (96 kW)
Kerb mass1,502 kg
Power to weight86 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Jaguar X-Type 2.0D 13020018.99 s16.74 s82.4 mph129 bhp
Mercedes-Benz C Class C 160 12920188.84 s16.76 s83.1 mph127 bhp
Volvo S90 2.0 D3 150 (2019)20198.93 s16.88 s82.6 mph148 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
Chevrolet 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 2000s5,138 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 Chevrolet Cruze 1.7 VCDi 132 0-60 time?
The Chevrolet Cruze 1.7 VCDi 132 reaches 60 mph in 8.90 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,225th quickest of the 14,946 cars in the set.
What is the Chevrolet Cruze 1.7 VCDi 132 quarter mile time?
16.69 s at 82.7 mph. It reaches the eighth mile in 10.74 s and clears the first 60 ft in 2.66 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Cruze 1.7 VCDi 132 have?
129 bhp and 1,502 kg, which is 86 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Cruze 1.7 VCDi 132?
Closest here on pace: Jaguar X-Type 2.0D 130 (8.99 s), Mercedes-Benz C Class C 160 129 (8.84 s), Volvo S90 2.0 D3 150 (2019) (8.93 s). Each one can be raced against the Chevrolet Cruze 1.7 VCDi 132 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 Chevrolet Cruze 1.7 VCDi 132 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.