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

Mitsubishi Space Star 1.2 MIVEC 80

The Mitsubishi Space Star 1.2 MIVEC 80 reaches 60 mph in 10.66 s (100 km/h in 11.29 s) and covers a standing quarter mile in 18.04 s, tripping the lights at 78.2 mph. It clears the first 60 ft in 3.06 s and the eighth mile in 11.74 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 Space Star 1.2 MIVEC 80 Daihatsu Gran Move 1.6 91

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 Space Star 1.2 MIVEC 80
0–60 mph10.66 s
0–100 km/h11.29 s
0–100 mph—
60 ft3.06 s
1/8 mile11.74 s
1/4 mile18.04 s
Trap speed78.2 mph

About the Space Star 1.2 MIVEC 80

The 2013 Mitsubishi Space Star 1.2 MIVEC 80 is a front-drive naturally aspirated car of 845 kg with 79 bhp, which works out at 94 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.06 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 11,196th quickest to 60 mph, and the 111th quickest of the 164 Mitsubishis here. Its 78.2 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 Space Star 1.2 MIVEC 80
Year2013
Power79 hp (59 kW)
Kerb mass845 kg
Power to weight94 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Daihatsu Gran Move 1.6 91199910.62 s18.08 s76.8 mph90 bhp
SEAT Leon 1.6 102200910.67 s18.03 s78.4 mph101 bhp
Aston Martin Cygnet 1.3 98201110.72 s17.94 s76.7 mph97 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
Mitsubishi 0-60 timesevery modelFastest small cars1,681 carsFastest cars of the 2010s4,541 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 Space Star 1.2 MIVEC 80 0-60 time?
The Mitsubishi Space Star 1.2 MIVEC 80 reaches 60 mph in 10.66 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,196th quickest of the 14,946 cars in the set.
What is the Mitsubishi Space Star 1.2 MIVEC 80 quarter mile time?
18.04 s at 78.2 mph. It reaches the eighth mile in 11.74 s and clears the first 60 ft in 3.06 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Space Star 1.2 MIVEC 80 have?
79 bhp and 845 kg, which is 94 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Space Star 1.2 MIVEC 80?
Closest here on pace: Daihatsu Gran Move 1.6 91 (10.62 s), SEAT Leon 1.6 102 (10.67 s), Aston Martin Cygnet 1.3 98 (10.72 s). Each one can be raced against the Mitsubishi Space Star 1.2 MIVEC 80 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 Space Star 1.2 MIVEC 80 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.