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

Chevrolet Cruze HB5 1.4 Turbo 140

The Chevrolet Cruze HB5 1.4 Turbo 140 reaches 60 mph in 8.48 s (100 km/h in 8.94 s) and covers a standing quarter mile in 16.32 s, tripping the lights at 84.9 mph. It clears the first 60 ft in 2.47 s and the eighth mile in 10.52 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 1.4 Turbo 140 Volvo V60 2.0 D3 163

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 1.4 Turbo 140
0–60 mph8.48 s
0–100 km/h8.94 s
0–100 mph—
60 ft2.47 s
1/8 mile10.52 s
1/4 mile16.32 s
Trap speed84.9 mph

About the Cruze HB5 1.4 Turbo 140

The 2011 Chevrolet Cruze HB5 1.4 Turbo 140 is a front-drive turbocharged saloon of 1,394 kg with 138 bhp, which works out at 99 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.47 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,453rd quickest to 60 mph, and the 100th quickest of the 199 Chevrolets here. Its 84.9 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 1.4 Turbo 140
Year2011
Power138 hp (103 kW)
Kerb mass1,394 kg
Power to weight99 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo V60 2.0 D3 16320108.45 s16.54 s84.1 mph161 bhp
Fiat Linea 1.4 12020068.35 s16.35 s84.5 mph118 bhp
Skoda Rapid 1.4 TSI 12220128.49 s16.58 s82.7 mph121 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 1.4 Turbo 140 0-60 time?
The Chevrolet Cruze HB5 1.4 Turbo 140 reaches 60 mph in 8.48 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,453rd quickest of the 14,946 cars in the set.
What is the Chevrolet Cruze HB5 1.4 Turbo 140 quarter mile time?
16.32 s at 84.9 mph. It reaches the eighth mile in 10.52 s and clears the first 60 ft in 2.47 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Cruze HB5 1.4 Turbo 140 have?
138 bhp and 1,394 kg, which is 99 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Cruze HB5 1.4 Turbo 140?
Closest here on pace: Volvo V60 2.0 D3 163 (8.45 s), Fiat Linea 1.4 120 (8.35 s), Skoda Rapid 1.4 TSI 122 (8.49 s). Each one can be raced against the Chevrolet Cruze HB5 1.4 Turbo 140 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 1.4 Turbo 140 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.