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

Mitsubishi Pajero 3dr 3.0 V6 141

The Mitsubishi Pajero 3dr 3.0 V6 141 reaches 60 mph in 11.14 s (100 km/h in 11.87 s) and covers a standing quarter mile in 18.42 s, tripping the lights at 75.2 mph. It clears the first 60 ft in 3.00 s and the eighth mile in 11.85 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 Pajero 3dr 3.0 V6 141 Suzuki Swift 5dr 1.2 ECO 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 Pajero 3dr 3.0 V6 141
0–60 mph11.14 s
0–100 km/h11.87 s
0–100 mph—
60 ft3.00 s
1/8 mile11.85 s
1/4 mile18.42 s
Trap speed75.2 mph

About the Pajero 3dr 3.0 V6 141

The 1982 Mitsubishi Pajero 3dr 3.0 V6 141 is an all-wheel-drive naturally aspirated car of 1,650 kg with 139 bhp, which works out at 85 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.00 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 11,841st quickest to 60 mph, and the 117th quickest of the 164 Mitsubishis here. Its 75.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 Pajero 3dr 3.0 V6 141
Year1982
Power139 hp (104 kW)
Kerb mass1,650 kg
Power to weight85 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed99 mph (159 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Suzuki Swift 5dr 1.2 ECO 90201411.18 s18.42 s75.8 mph89 bhp
Suzuki Splash 1.2 85200811.21 s18.40 s76.6 mph83 bhp
Audi A2 1.4 75199911.20 s18.40 s76.5 mph74 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 1980s1,057 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 Pajero 3dr 3.0 V6 141 0-60 time?
The Mitsubishi Pajero 3dr 3.0 V6 141 reaches 60 mph in 11.14 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,841st quickest of the 14,946 cars in the set.
What is the Mitsubishi Pajero 3dr 3.0 V6 141 quarter mile time?
18.42 s at 75.2 mph. It reaches the eighth mile in 11.85 s and clears the first 60 ft in 3.00 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mitsubishi Pajero 3dr 3.0 V6 141 have?
139 bhp and 1,650 kg, which is 85 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 5 gears and a quoted top speed of 159 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mitsubishi Pajero 3dr 3.0 V6 141?
Closest here on pace: Suzuki Swift 5dr 1.2 ECO 90 (11.18 s), Suzuki Splash 1.2 85 (11.21 s), Audi A2 1.4 75 (11.20 s). Each one can be raced against the Mitsubishi Pajero 3dr 3.0 V6 141 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 Pajero 3dr 3.0 V6 141 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.