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

Mitsubishi Starion 2.6 Turbo 155

The Mitsubishi Starion 2.6 Turbo 155 reaches 60 mph in 6.95 s (100 km/h in 7.84 s) and covers a standing quarter mile in 15.53 s, tripping the lights at 89.7 mph. It clears the first 60 ft in 2.50 s and the eighth mile in 10.05 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 Starion 2.6 Turbo 155 Peugeot 207 - 3dr 1.6 THP 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 Mitsubishi Starion 2.6 Turbo 155
0–60 mph6.95 s
0–100 km/h7.84 s
0–100 mph—
60 ft2.50 s
1/8 mile10.05 s
1/4 mile15.53 s
Trap speed89.7 mph

About the Starion 2.6 Turbo 155

The 1982 Mitsubishi Starion 2.6 Turbo 155 is a rear-drive turbocharged car of 1,325 kg with 153 bhp, which works out at 115 bhp per tonne. Rear drive and 115 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.50 s. Against the 14,946 cars in the set it is the 4,550th quickest to 60 mph, and the 29th quickest of the 164 Mitsubishis here. Its 89.7 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 Starion 2.6 Turbo 155
Year1982
Power153 hp (114 kW)
Kerb mass1,325 kg
Power to weight115 bhp/t
DrivetrainRear drive
Gears5
EngineTurbocharged
Top speed134 mph (216 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot 207 - 3dr 1.6 THP 15020096.89 s15.51 s90.5 mph148 bhp
Fiat Croma 2.0 Turbo 15019916.97 s15.57 s90.0 mph148 bhp
MINI Hatch Cooper 1.5 13620187.01 s15.52 s89.8 mph134 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 7 seconds4,651 cars0-100 km/h under 8 seconds5,602 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 hatchbacks4,513 carsFastest cars of the 1980s1,057 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 Starion 2.6 Turbo 155 0-60 time?
The Mitsubishi Starion 2.6 Turbo 155 reaches 60 mph in 6.95 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,550th quickest of the 14,946 cars in the set.
What is the Mitsubishi Starion 2.6 Turbo 155 quarter mile time?
15.53 s at 89.7 mph. It reaches the eighth mile in 10.05 s and clears the first 60 ft in 2.50 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Starion 2.6 Turbo 155 have?
153 bhp and 1,325 kg, which is 115 bhp per tonne. It is rear-drive, turbocharged, with 5 gears and a quoted top speed of 216 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Starion 2.6 Turbo 155?
Closest here on pace: Peugeot 207 - 3dr 1.6 THP 150 (6.89 s), Fiat Croma 2.0 Turbo 150 (6.97 s), MINI Hatch Cooper 1.5 136 (7.01 s). Each one can be raced against the Mitsubishi Starion 2.6 Turbo 155 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 Starion 2.6 Turbo 155 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.