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

Mitsubishi Space Star 1.9 DI-D 102

The Mitsubishi Space Star 1.9 DI-D 102 reaches 60 mph in 10.88 s (100 km/h in 11.56 s) and covers a standing quarter mile in 18.02 s, tripping the lights at 76.4 mph. It clears the first 60 ft in 2.88 s and the eighth mile in 11.59 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.9 DI-D 102 Dacia Sandero 2 1.5 dCI 90

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.9 DI-D 102
0–60 mph10.88 s
0–100 km/h11.56 s
0–100 mph—
60 ft2.88 s
1/8 mile11.59 s
1/4 mile18.02 s
Trap speed76.4 mph

About the Space Star 1.9 DI-D 102

The 2002 Mitsubishi Space Star 1.9 DI-D 102 is a front-drive turbodiesel car of 1,220 kg with 101 bhp, which works out at 82 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.88 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,495th quickest to 60 mph, and the 115th quickest of the 164 Mitsubishis here. Its 76.4 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.9 DI-D 102
Year2002
Power101 hp (75 kW)
Kerb mass1,220 kg
Power to weight82 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dacia Sandero 2 1.5 dCI 90201210.94 s18.09 s75.8 mph89 bhp
SEAT Arosa 1.4 TDI 75 (2001)200110.91 s18.09 s75.5 mph74 bhp
Audi A3 1.6 102 (2008)200810.76 s18.09 s78.4 mph101 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 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 Mitsubishi Space Star 1.9 DI-D 102 0-60 time?
The Mitsubishi Space Star 1.9 DI-D 102 reaches 60 mph in 10.88 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,495th quickest of the 14,946 cars in the set.
What is the Mitsubishi Space Star 1.9 DI-D 102 quarter mile time?
18.02 s at 76.4 mph. It reaches the eighth mile in 11.59 s and clears the first 60 ft in 2.88 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Space Star 1.9 DI-D 102 have?
101 bhp and 1,220 kg, which is 82 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Space Star 1.9 DI-D 102?
Closest here on pace: Dacia Sandero 2 1.5 dCI 90 (10.94 s), SEAT Arosa 1.4 TDI 75 (2001) (10.91 s), Audi A3 1.6 102 (2008) (10.76 s). Each one can be raced against the Mitsubishi Space Star 1.9 DI-D 102 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.9 DI-D 102 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.