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

Chevrolet Cruze HB5 2.0 TD 163

The Chevrolet Cruze HB5 2.0 TD 163 reaches 60 mph in 8.88 s (100 km/h in 9.49 s) and covers a standing quarter mile in 16.84 s, tripping the lights at 82.3 mph. It clears the first 60 ft in 2.61 s and the eighth mile in 10.81 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 HB5 2.0 TD 163 Lancia Kappa 2.0 146

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 HB5 2.0 TD 163
0–60 mph8.88 s
0–100 km/h9.49 s
0–100 mph—
60 ft2.61 s
1/8 mile10.81 s
1/4 mile16.84 s
Trap speed82.3 mph

About the Cruze HB5 2.0 TD 163

The 2011 Chevrolet Cruze HB5 2.0 TD 163 is a front-drive turbodiesel saloon of 1,585 kg with 161 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.61 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,198th quickest to 60 mph, and the 111th quickest of the 199 Chevrolets here. Its 82.3 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 HB5 2.0 TD 163
Year2011
Power161 hp (120 kW)
Kerb mass1,585 kg
Power to weight102 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Kappa 2.0 14619958.93 s16.78 s84.7 mph143 bhp
Holden Vectra 1.9 CDTI 15020028.86 s16.80 s83.4 mph148 bhp
Honda Civic Sedan 1.4 9019878.91 s16.94 s81.8 mph89 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 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 Chevrolet Cruze HB5 2.0 TD 163 0-60 time?
The Chevrolet Cruze HB5 2.0 TD 163 reaches 60 mph in 8.88 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,198th quickest of the 14,946 cars in the set.
What is the Chevrolet Cruze HB5 2.0 TD 163 quarter mile time?
16.84 s at 82.3 mph. It reaches the eighth mile in 10.81 s and clears the first 60 ft in 2.61 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Cruze HB5 2.0 TD 163 have?
161 bhp and 1,585 kg, which is 102 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Cruze HB5 2.0 TD 163?
Closest here on pace: Lancia Kappa 2.0 146 (8.93 s), Holden Vectra 1.9 CDTI 150 (8.86 s), Honda Civic Sedan 1.4 90 (8.91 s). Each one can be raced against the Chevrolet Cruze HB5 2.0 TD 163 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 HB5 2.0 TD 163 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.