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

Ssangyong Korando 2.3 TD 101

The Ssangyong Korando 2.3 TD 101 reaches 60 mph in 18.04 s (100 km/h in 19.45 s) and covers a standing quarter mile in 21.15 s, tripping the lights at 64.5 mph. It clears the first 60 ft in 3.30 s and the eighth mile in 13.49 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.

Ssangyong Korando 2.3 TD 101 Suzuki Vitara 2.0 Turbo D 87

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 Ssangyong Korando 2.3 TD 101
0–60 mph18.04 s
0–100 km/h19.45 s
0–100 mph—
60 ft3.30 s
1/8 mile13.49 s
1/4 mile21.15 s
Trap speed64.5 mph

About the Korando 2.3 TD 101

The 1997 Ssangyong Korando 2.3 TD 101 is an all-wheel-drive turbodiesel SUV of 1,750 kg with 99 bhp, which works out at 57 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.30 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,824th quickest to 60 mph, and the 18th quickest of the 20 Ssangyongs here. Its 64.5 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 Ssangyong Korando 2.3 TD 101
Year1997
Power99 hp (74 kW)
Kerb mass1,750 kg
Power to weight57 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed87 mph (140 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Suzuki Vitara 2.0 Turbo D 87199117.96 s21.17 s65.1 mph86 bhp
Suzuki Escudo / Grand Vitara 5dr 2.0 TD 85199817.89 s21.10 s64.7 mph86 bhp
Land Rover Range Rover 2.5 TD 121198817.69 s21.05 s65.4 mph119 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
Ssangyong 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 Ssangyong Korando 2.3 TD 101 0-60 time?
The Ssangyong Korando 2.3 TD 101 reaches 60 mph in 18.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,824th quickest of the 14,946 cars in the set.
What is the Ssangyong Korando 2.3 TD 101 quarter mile time?
21.15 s at 64.5 mph. It reaches the eighth mile in 13.49 s and clears the first 60 ft in 3.30 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ssangyong Korando 2.3 TD 101 have?
99 bhp and 1,750 kg, which is 57 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 gears and a quoted top speed of 140 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ssangyong Korando 2.3 TD 101?
Closest here on pace: Suzuki Vitara 2.0 Turbo D 87 (17.96 s), Suzuki Escudo / Grand Vitara 5dr 2.0 TD 85 (17.89 s), Land Rover Range Rover 2.5 TD 121 (17.69 s). Each one can be raced against the Ssangyong Korando 2.3 TD 101 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 Ssangyong Korando 2.3 TD 101 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.