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

Mitsubishi Galant 2.4 GDI 150

The Mitsubishi Galant 2.4 GDI 150 reaches 60 mph in 8.84 s (100 km/h in 9.34 s) and covers a standing quarter mile in 16.71 s, tripping the lights at 85.0 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 10.92 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.

Mitsubishi Galant 2.4 GDI 150 Peugeot 604 2.8 155

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 Mitsubishi Galant 2.4 GDI 150
0–60 mph8.84 s
0–100 km/h9.34 s
0–100 mph—
60 ft2.86 s
1/8 mile10.92 s
1/4 mile16.71 s
Trap speed85.0 mph

About the Galant 2.4 GDI 150

The 1997 Mitsubishi Galant 2.4 GDI 150 is a front-drive naturally aspirated saloon of 1,295 kg with 148 bhp, which works out at 114 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.86 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 8,116th quickest to 60 mph, and the 49th quickest of the 164 Mitsubishis here. Its 85.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 Mitsubishi Galant 2.4 GDI 150
Year1997
Power148 hp (110 kW)
Kerb mass1,295 kg
Power to weight114 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed127 mph (205 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot 604 2.8 15519758.83 s16.77 s83.7 mph153 bhp
Renault 21 2.0 12019868.84 s16.73 s84.6 mph118 bhp
Nissan Bluebird Sedan 1.8 Turbo 13519868.89 s16.72 s82.4 mph133 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
Mitsubishi 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 1990s2,649 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 Mitsubishi Galant 2.4 GDI 150 0-60 time?
The Mitsubishi Galant 2.4 GDI 150 reaches 60 mph in 8.84 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,116th quickest of the 14,946 cars in the set.
What is the Mitsubishi Galant 2.4 GDI 150 quarter mile time?
16.71 s at 85.0 mph. It reaches the eighth mile in 10.92 s and clears the first 60 ft in 2.86 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Galant 2.4 GDI 150 have?
148 bhp and 1,295 kg, which is 114 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 205 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Galant 2.4 GDI 150?
Closest here on pace: Peugeot 604 2.8 155 (8.83 s), Renault 21 2.0 120 (8.84 s), Nissan Bluebird Sedan 1.8 Turbo 135 (8.89 s). Each one can be raced against the Mitsubishi Galant 2.4 GDI 150 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 Mitsubishi Galant 2.4 GDI 150 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.