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

Mitsubishi Colt 5dr 1.3 95 (2004)

The Mitsubishi Colt 5dr 1.3 95 (2004) reaches 60 mph in 10.11 s (100 km/h in 10.70 s) and covers a standing quarter mile in 17.69 s, tripping the lights at 79.4 mph. It clears the first 60 ft in 2.97 s and the eighth mile in 11.48 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 Colt 5dr 1.3 95 (2004) Chevrolet Aveo/Kalos 5dr 1.6 105

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 Colt 5dr 1.3 95 (2004)
0–60 mph10.11 s
0–100 km/h10.70 s
0–100 mph—
60 ft2.97 s
1/8 mile11.48 s
1/4 mile17.69 s
Trap speed79.4 mph

About the Colt 5dr 1.3 95

The 2004 Mitsubishi Colt 5dr 1.3 95 (2004) is a front-drive naturally aspirated car of 945 kg with 94 bhp, which works out at 99 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.97 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 10,354th quickest to 60 mph, and the 94th quickest of the 164 Mitsubishis here. Its 79.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 Colt 5dr 1.3 95 (2004)
Year2004
Power94 hp (70 kW)
Kerb mass945 kg
Power to weight99 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Aveo/Kalos 5dr 1.6 105200410.12 s17.67 s79.9 mph103 bhp
Honda Civic 1.5 ISI199210.12 s17.69 s79.6 mph90 bhp
Hyundai Lantra 1.6i 114 (1991)199110.11 s17.69 s79.4 mph113 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 Colt 5dr 1.3 95 (2004) 0-60 time?
The Mitsubishi Colt 5dr 1.3 95 (2004) reaches 60 mph in 10.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,354th quickest of the 14,946 cars in the set.
What is the Mitsubishi Colt 5dr 1.3 95 (2004) quarter mile time?
17.69 s at 79.4 mph. It reaches the eighth mile in 11.48 s and clears the first 60 ft in 2.97 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Colt 5dr 1.3 95 (2004) have?
94 bhp and 945 kg, which is 99 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 Colt 5dr 1.3 95 (2004)?
Closest here on pace: Chevrolet Aveo/Kalos 5dr 1.6 105 (10.12 s), Honda Civic 1.5 ISI (10.12 s), Hyundai Lantra 1.6i 114 (1991) (10.11 s). Each one can be raced against the Mitsubishi Colt 5dr 1.3 95 (2004) 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 Colt 5dr 1.3 95 (2004) 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.