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

Ssangyong Korando 3.2 V6 220

The Ssangyong Korando 3.2 V6 220 reaches 60 mph in 8.92 s (100 km/h in 9.43 s) and covers a standing quarter mile in 17.15 s, tripping the lights at 82.9 mph. It clears the first 60 ft in 3.00 s and the eighth mile in 11.21 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 3.2 V6 220 Volvo XC60 3.2 243

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 3.2 V6 220
0–60 mph8.92 s
0–100 km/h9.43 s
0–100 mph—
60 ft3.00 s
1/8 mile11.21 s
1/4 mile17.15 s
Trap speed82.9 mph

About the Korando 3.2 V6 220

The 1997 Ssangyong Korando 3.2 V6 220 is an all-wheel-drive naturally aspirated SUV of 1,840 kg with 217 bhp, which works out at 118 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 8,264th quickest to 60 mph, and the quickest of the 20 Ssangyongs here. Its 82.9 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 3.2 V6 220
Year1997
Power217 hp (162 kW)
Kerb mass1,840 kg
Power to weight118 bhp/t
DrivetrainAll-wheel drive
Gears4
EngineNaturally aspirated
Top speed106 mph (171 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo XC60 3.2 24320088.95 s16.95 s83.3 mph240 bhp
Subaru Forester 2.5 16720028.93 s16.82 s83.7 mph165 bhp
Subaru Outback 2.5 16520058.93 s16.80 s84.1 mph162 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 cars0-100 km/h under 10 seconds9,062 carsSlower 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 3.2 V6 220 0-60 time?
The Ssangyong Korando 3.2 V6 220 reaches 60 mph in 8.92 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,264th quickest of the 14,946 cars in the set.
What is the Ssangyong Korando 3.2 V6 220 quarter mile time?
17.15 s at 82.9 mph. It reaches the eighth mile in 11.21 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 Ssangyong Korando 3.2 V6 220 have?
217 bhp and 1,840 kg, which is 118 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 4 gears and a quoted top speed of 171 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ssangyong Korando 3.2 V6 220?
Closest here on pace: Volvo XC60 3.2 243 (8.95 s), Subaru Forester 2.5 167 (8.93 s), Subaru Outback 2.5 165 (8.93 s). Each one can be raced against the Ssangyong Korando 3.2 V6 220 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 3.2 V6 220 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.