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

Chevrolet Cruze Wagon 1.8 141

The Chevrolet Cruze Wagon 1.8 141 reaches 60 mph in 10.38 s (100 km/h in 11.07 s) and covers a standing quarter mile in 17.76 s, tripping the lights at 78.5 mph. It clears the first 60 ft in 2.90 s and the eighth mile in 11.48 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 Wagon 1.8 141 Cadillac BLS Wagon 1.9D 150

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 Wagon 1.8 141
0–60 mph10.38 s
0–100 km/h11.07 s
0–100 mph—
60 ft2.90 s
1/8 mile11.48 s
1/4 mile17.76 s
Trap speed78.5 mph

About the Cruze Wagon 1.8 141

The 2012 Chevrolet Cruze Wagon 1.8 141 is a front-drive naturally aspirated estate of 1,400 kg with 139 bhp, which works out at 100 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.90 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 10,738th quickest to 60 mph, and the 143rd quickest of the 199 Chevrolets here. Its 78.5 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 Wagon 1.8 141
Year2012
Power139 hp (104 kW)
Kerb mass1,400 kg
Power to weight100 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed119 mph (192 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Cadillac BLS Wagon 1.9D 150200710.38 s17.61 s78.1 mph148 bhp
Honda Accord Tourer - EU 2.0 i-VTEC 150201110.22 s17.79 s79.7 mph148 bhp
Mazda 6/Atenza Wagon 2.0 16V 147200710.18 s17.80 s80.9 mph145 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Chevrolet 0-60 timesevery modelFastest estate cars1,484 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 Wagon 1.8 141 0-60 time?
The Chevrolet Cruze Wagon 1.8 141 reaches 60 mph in 10.38 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,738th quickest of the 14,946 cars in the set.
What is the Chevrolet Cruze Wagon 1.8 141 quarter mile time?
17.76 s at 78.5 mph. It reaches the eighth mile in 11.48 s and clears the first 60 ft in 2.90 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Cruze Wagon 1.8 141 have?
139 bhp and 1,400 kg, which is 100 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 192 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Cruze Wagon 1.8 141?
Closest here on pace: Cadillac BLS Wagon 1.9D 150 (10.38 s), Honda Accord Tourer - EU 2.0 i-VTEC 150 (10.22 s), Mazda 6/Atenza Wagon 2.0 16V 147 (10.18 s). Each one can be raced against the Chevrolet Cruze Wagon 1.8 141 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 Wagon 1.8 141 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.