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

Chevrolet Chevelle Malibu SS 3.2 122

The Chevrolet Chevelle Malibu SS 3.2 122 reaches 60 mph in 13.34 s (100 km/h in 14.08 s) and covers a standing quarter mile in 19.93 s, tripping the lights at 75.0 mph. It clears the first 60 ft in 3.43 s and the eighth mile in 13.34 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 Chevelle Malibu SS 3.2 122 Bristol 405 2.0 107

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 Chevelle Malibu SS 3.2 122
0–60 mph13.34 s
0–100 km/h14.08 s
0–100 mph—
60 ft3.43 s
1/8 mile13.34 s
1/4 mile19.93 s
Trap speed75.0 mph

About the Chevelle Malibu SS 3.2 122

The 1964 Chevrolet Chevelle Malibu SS 3.2 122 is a rear-drive naturally aspirated saloon of 1,365 kg with 121 bhp, which works out at 88 bhp per tonne. Rear drive and 88 bhp per tonne make the launch the hard part of the run: 60 ft takes 3.43 s. Against the 14,946 cars in the set it is the 13,793rd quickest to 60 mph, and the 193rd quickest of the 199 Chevrolets here. It traps higher than its 0-60 suggests — 75.0 mph, the 12,603rd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Chevrolet Chevelle Malibu SS 3.2 122
Year1964
Power121 hp (90 kW)
Kerb mass1,365 kg
Power to weight88 bhp/t
DrivetrainRear drive
Gears3
EngineNaturally aspirated
Top speed96 mph (154 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Bristol 405 2.0 107195513.33 s19.63 s72.8 mph105 bhp
Lincoln Continental 3.8 V6 112198213.39 s20.02 s73.1 mph113 bhp
Proton Waja/Impian 1.6 103200113.51 s20.14 s74.8 mph102 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 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 Chevelle Malibu SS 3.2 122 0-60 time?
The Chevrolet Chevelle Malibu SS 3.2 122 reaches 60 mph in 13.34 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 13,793rd quickest of the 14,946 cars in the set.
What is the Chevrolet Chevelle Malibu SS 3.2 122 quarter mile time?
19.93 s at 75.0 mph. It reaches the eighth mile in 13.34 s and clears the first 60 ft in 3.43 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Chevelle Malibu SS 3.2 122 have?
121 bhp and 1,365 kg, which is 88 bhp per tonne. It is rear-drive, naturally aspirated, with 3 gears and a quoted top speed of 154 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Chevelle Malibu SS 3.2 122?
Closest here on pace: Bristol 405 2.0 107 (13.33 s), Lincoln Continental 3.8 V6 112 (13.39 s), Proton Waja/Impian 1.6 103 (13.51 s). Each one can be raced against the Chevrolet Chevelle Malibu SS 3.2 122 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 Chevelle Malibu SS 3.2 122 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.