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

Mitsubishi Lancer 1.8 DI-D 116

The Mitsubishi Lancer 1.8 DI-D 116 reaches 60 mph in 9.64 s (100 km/h in 10.20 s) and covers a standing quarter mile in 17.09 s, tripping the lights at 80.2 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.97 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 Lancer 1.8 DI-D 116 Holden Vectra Sedan 2.2 DTI 126

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 Lancer 1.8 DI-D 116
0–60 mph9.64 s
0–100 km/h10.20 s
0–100 mph—
60 ft2.55 s
1/8 mile10.97 s
1/4 mile17.09 s
Trap speed80.2 mph

About the Lancer 1.8 DI-D 116

The 2007 Mitsubishi Lancer 1.8 DI-D 116 is a front-drive turbodiesel saloon of 1,360 kg with 114 bhp, which works out at 84 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 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 9,521st quickest to 60 mph, and the 77th quickest of the 164 Mitsubishis here. Its 80.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 Lancer 1.8 DI-D 116
Year2007
Power114 hp (85 kW)
Kerb mass1,360 kg
Power to weight84 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed119 mph (192 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Vectra Sedan 2.2 DTI 12619959.55 s17.07 s81.4 mph123 bhp
Skoda Rapid 1.6 TDI 10520129.61 s17.21 s79.9 mph103 bhp
Skoda Rapid 1.6 TDI Green Tec 10520129.61 s17.21 s79.9 mph103 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 10 seconds10,136 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 saloon cars3,808 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 Lancer 1.8 DI-D 116 0-60 time?
The Mitsubishi Lancer 1.8 DI-D 116 reaches 60 mph in 9.64 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,521st quickest of the 14,946 cars in the set.
What is the Mitsubishi Lancer 1.8 DI-D 116 quarter mile time?
17.09 s at 80.2 mph. It reaches the eighth mile in 10.97 s and clears the first 60 ft in 2.55 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Lancer 1.8 DI-D 116 have?
114 bhp and 1,360 kg, which is 84 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 192 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Lancer 1.8 DI-D 116?
Closest here on pace: Holden Vectra Sedan 2.2 DTI 126 (9.55 s), Skoda Rapid 1.6 TDI 105 (9.61 s), Skoda Rapid 1.6 TDI Green Tec 105 (9.61 s). Each one can be raced against the Mitsubishi Lancer 1.8 DI-D 116 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 Lancer 1.8 DI-D 116 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.