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

Chevrolet Cavalier 2.2 141

The Chevrolet Cavalier 2.2 141 reaches 60 mph in 9.39 s (100 km/h in 9.92 s) and covers a standing quarter mile in 17.47 s, tripping the lights at 82.4 mph. It clears the first 60 ft in 3.08 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 Cavalier 2.2 141 Saab 9-5 SportCombi 2.3 T 185

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 Cavalier 2.2 141
0–60 mph9.39 s
0–100 km/h9.92 s
0–100 mph—
60 ft3.08 s
1/8 mile11.48 s
1/4 mile17.47 s
Trap speed82.4 mph

About the Cavalier 2.2 141

The 2003 Chevrolet Cavalier 2.2 141 is a front-drive naturally aspirated saloon of 1,191 kg with 139 bhp, which works out at 117 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.08 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 9,124th quickest to 60 mph, and the 123rd quickest of the 199 Chevrolets here. Its 82.4 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 Cavalier 2.2 141
Year2003
Power139 hp (104 kW)
Kerb mass1,191 kg
Power to weight117 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Saab 9-5 SportCombi 2.3 T 18519989.40 s17.29 s84.3 mph182 bhp
Subaru Forester 2.5 17120089.33 s17.37 s84.0 mph169 bhp
Lincoln Town Car 4.6 V8 LONG 23920089.38 s17.29 s87.1 mph239 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 Cavalier 2.2 141 0-60 time?
The Chevrolet Cavalier 2.2 141 reaches 60 mph in 9.39 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,124th quickest of the 14,946 cars in the set.
What is the Chevrolet Cavalier 2.2 141 quarter mile time?
17.47 s at 82.4 mph. It reaches the eighth mile in 11.48 s and clears the first 60 ft in 3.08 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Cavalier 2.2 141 have?
139 bhp and 1,191 kg, which is 117 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 175 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Cavalier 2.2 141?
Closest here on pace: Saab 9-5 SportCombi 2.3 T 185 (9.40 s), Subaru Forester 2.5 171 (9.33 s), Lincoln Town Car 4.6 V8 LONG 239 (9.38 s). Each one can be raced against the Chevrolet Cavalier 2.2 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 Cavalier 2.2 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.