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

Chevrolet Malibu Sedan 2.2 145

The Chevrolet Malibu Sedan 2.2 145 reaches 60 mph in 10.04 s (100 km/h in 10.61 s) and covers a standing quarter mile in 17.92 s, tripping the lights at 81.0 mph. It clears the first 60 ft in 3.17 s and the eighth mile in 11.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 Malibu Sedan 2.2 145 Chrysler Concorde 3.3 V6 153

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 Malibu Sedan 2.2 145
0–60 mph10.04 s
0–100 km/h10.61 s
0–100 mph—
60 ft3.17 s
1/8 mile11.81 s
1/4 mile17.92 s
Trap speed81.0 mph

About the Malibu Sedan 2.2 145

The 2003 Chevrolet Malibu Sedan 2.2 145 is a front-drive naturally aspirated saloon of 1,440 kg with 143 bhp, which works out at 100 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.17 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,268th quickest to 60 mph, and the 137th quickest of the 199 Chevrolets here. Its 81.0 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 Malibu Sedan 2.2 145
Year2003
Power143 hp (107 kW)
Kerb mass1,440 kg
Power to weight100 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chrysler Concorde 3.3 V6 153199310.06 s17.91 s81.6 mph153 bhp
Chrysler Saratoga 3.0 V6 141198910.07 s17.91 s81.8 mph139 bhp
Honda Accord Aerodeck 2.2 145199310.10 s17.88 s83.4 mph143 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 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 Malibu Sedan 2.2 145 0-60 time?
The Chevrolet Malibu Sedan 2.2 145 reaches 60 mph in 10.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,268th quickest of the 14,946 cars in the set.
What is the Chevrolet Malibu Sedan 2.2 145 quarter mile time?
17.92 s at 81.0 mph. It reaches the eighth mile in 11.81 s and clears the first 60 ft in 3.17 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Malibu Sedan 2.2 145 have?
143 bhp and 1,440 kg, which is 100 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 Malibu Sedan 2.2 145?
Closest here on pace: Chrysler Concorde 3.3 V6 153 (10.06 s), Chrysler Saratoga 3.0 V6 141 (10.07 s), Honda Accord Aerodeck 2.2 145 (10.10 s). Each one can be raced against the Chevrolet Malibu Sedan 2.2 145 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 Malibu Sedan 2.2 145 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.