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

Mitsubishi Mirage 1.2 MIVEC CVT 78

The Mitsubishi Mirage 1.2 MIVEC CVT 78 reaches 60 mph in 12.17 s (100 km/h in 13.06 s) and covers a standing quarter mile in 18.82 s, tripping the lights at 73.4 mph. It clears the first 60 ft in 3.01 s and the eighth mile in 12.11 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 Mirage 1.2 MIVEC CVT 78 Citroen C3 PureTech 83 (Mk3)

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 Mirage 1.2 MIVEC CVT 78
0–60 mph12.17 s
0–100 km/h13.06 s
0–100 mph—
60 ft3.01 s
1/8 mile12.11 s
1/4 mile18.82 s
Trap speed73.4 mph

About the Mirage 1.2 MIVEC CVT 78

The 2019 Mitsubishi Mirage 1.2 MIVEC CVT 78 is a front-drive naturally aspirated car of 905 kg with 76 bhp, which works out at 84 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.01 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 12,979th quickest to 60 mph, and the 132nd quickest of the 164 Mitsubishis here. Its 73.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 Mirage 1.2 MIVEC CVT 78
Year2019
Power76 hp (57 kW)
Kerb mass905 kg
Power to weight84 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed107 mph (172 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Citroen C3 PureTech 83 (Mk3)201812.11 s18.95 s74.3 mph82 bhp
Suzuki Swift 3dr 1.2 94201412.19 s19.01 s73.9 mph93 bhp
Subaru Trezia 1.3 99201012.09 s18.67 s74.2 mph98 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 Mirage 1.2 MIVEC CVT 78 0-60 time?
The Mitsubishi Mirage 1.2 MIVEC CVT 78 reaches 60 mph in 12.17 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,979th quickest of the 14,946 cars in the set.
What is the Mitsubishi Mirage 1.2 MIVEC CVT 78 quarter mile time?
18.82 s at 73.4 mph. It reaches the eighth mile in 12.11 s and clears the first 60 ft in 3.01 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Mirage 1.2 MIVEC CVT 78 have?
76 bhp and 905 kg, which is 84 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 172 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Mirage 1.2 MIVEC CVT 78?
Closest here on pace: Citroen C3 PureTech 83 (Mk3) (12.11 s), Suzuki Swift 3dr 1.2 94 (12.19 s), Subaru Trezia 1.3 99 (12.09 s). Each one can be raced against the Mitsubishi Mirage 1.2 MIVEC CVT 78 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 Mirage 1.2 MIVEC CVT 78 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.