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

Land Rover Discovery 2.5 TDI 113

The Land Rover Discovery 2.5 TDI 113 reaches 60 mph in 16.75 s (100 km/h in 17.97 s) and covers a standing quarter mile in 20.63 s, tripping the lights at 66.2 mph. It clears the first 60 ft in 3.23 s and the eighth mile in 13.18 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 Discovery 2.5 TDI 113 Land Rover Defender 110 2.5 TDI 113

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 Discovery 2.5 TDI 113
0–60 mph16.75 s
0–100 km/h17.97 s
0–100 mph—
60 ft3.23 s
1/8 mile13.18 s
1/4 mile20.63 s
Trap speed66.2 mph

About the Discovery 2.5 TDI 113

The 1994 Land Rover Discovery 2.5 TDI 113 is an all-wheel-drive turbodiesel SUV of 1,985 kg with 111 bhp, which works out at 56 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.23 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,721st quickest to 60 mph, and the 83rd quickest of the 86 Land Rovers here. Its 66.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 Land Rover Discovery 2.5 TDI 113
Year1994
Power111 hp (83 kW)
Kerb mass1,985 kg
Power to weight56 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed91 mph (146 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Defender 110 2.5 TDI 113199116.73 s20.58 s65.6 mph111 bhp
Aro 10 1.9 94198016.51 s20.42 s65.1 mph93 bhp
Dacia 1320 1.3 54198816.82 s20.92 s66.4 mph54 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 Discovery 2.5 TDI 113 0-60 time?
The Land Rover Discovery 2.5 TDI 113 reaches 60 mph in 16.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,721st quickest of the 14,946 cars in the set.
What is the Land Rover Discovery 2.5 TDI 113 quarter mile time?
20.63 s at 66.2 mph. It reaches the eighth mile in 13.18 s and clears the first 60 ft in 3.23 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Land Rover Discovery 2.5 TDI 113 have?
111 bhp and 1,985 kg, which is 56 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 gears and a quoted top speed of 146 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Land Rover Discovery 2.5 TDI 113?
Closest here on pace: Land Rover Defender 110 2.5 TDI 113 (16.73 s), Aro 10 1.9 94 (16.51 s), Dacia 1320 1.3 54 (16.82 s). Each one can be raced against the Land Rover Discovery 2.5 TDI 113 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 Discovery 2.5 TDI 113 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.