← My Auto Racer All cars Land Rover 0-60 Comparisons Answers

Land Rover Defender 110 2.5 TD 86

The Land Rover Defender 110 2.5 TD 86 reaches 60 mph in 20.55 s and covers a standing quarter mile in 21.69 s, tripping the lights at 60.3 mph. It clears the first 60 ft in 3.18 s and the eighth mile in 13.71 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.

Land Rover Defender 110 2.5 TD 86 Fiat Panda 0.8 34

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 Land Rover Defender 110 2.5 TD 86
0–60 mph20.55 s
0–100 km/h—
0–100 mph—
60 ft3.18 s
1/8 mile13.71 s
1/4 mile21.69 s
Trap speed60.3 mph

About the Defender 110 2.5 TD 86

The 1991 Land Rover Defender 110 2.5 TD 86 is an all-wheel-drive turbodiesel SUV of 1,850 kg with 84 bhp, which works out at 46 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.18 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 14,914th quickest to 60 mph, and the 86th quickest of the 86 Land Rovers here. Its 60.3 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 Land Rover Defender 110 2.5 TD 86
Year1991
Power84 hp (63 kW)
Kerb mass1,850 kg
Power to weight46 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed73 mph (118 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Fiat Panda 0.8 34198620.63 s22.67 s62.4 mph34 bhp
Ssangyong Korando 2.9 D 95199721.16 s22.70 s62.0 mph94 bhp
Jeep Cherokee 2.1 TD 85198420.24 s23.16 s64.0 mph84 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
Land Rover 0-60 timesevery modelFastest SUVs2,049 carsFastest cars of the 1990s2,649 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 Land Rover Defender 110 2.5 TD 86 0-60 time?
The Land Rover Defender 110 2.5 TD 86 reaches 60 mph in 20.55 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,914th quickest of the 14,946 cars in the set.
What is the Land Rover Defender 110 2.5 TD 86 quarter mile time?
21.69 s at 60.3 mph. It reaches the eighth mile in 13.71 s and clears the first 60 ft in 3.18 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Land Rover Defender 110 2.5 TD 86 have?
84 bhp and 1,850 kg, which is 46 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 gears and a quoted top speed of 118 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Land Rover Defender 110 2.5 TD 86?
Closest here on pace: Fiat Panda 0.8 34 (20.63 s), Ssangyong Korando 2.9 D 95 (21.16 s), Jeep Cherokee 2.1 TD 85 (20.24 s). Each one can be raced against the Land Rover Defender 110 2.5 TD 86 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 Land Rover Defender 110 2.5 TD 86 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.