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

Ssangyong Korando 2.0 178

The Ssangyong Korando 2.0 178 reaches 60 mph in 8.96 s (100 km/h in 9.51 s) and covers a standing quarter mile in 16.65 s, tripping the lights at 80.9 mph. It clears the first 60 ft in 2.32 s and the eighth mile in 10.56 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.0 178 Jeep Compass 1.4 MultiAir 140

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.0 178
0–60 mph8.96 s
0–100 km/h9.51 s
0–100 mph—
60 ft2.32 s
1/8 mile10.56 s
1/4 mile16.65 s
Trap speed80.9 mph

About the Korando 2.0 178

The 2017 Ssangyong Korando 2.0 178 is an all-wheel-drive turbodiesel SUV of 1,828 kg with 176 bhp, which works out at 96 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.32 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,364th quickest to 60 mph, and the 3rd quickest of the 20 Ssangyongs here. It leaves better than it pulls: 80.9 mph at the lights is only the 9,562nd highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Ssangyong Korando 2.0 178
Year2017
Power176 hp (131 kW)
Kerb mass1,828 kg
Power to weight96 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Jeep Compass 1.4 MultiAir 14020178.94 s16.64 s83.3 mph138 bhp
Vauxhall Mokka 1.4 Turbo 14020128.97 s16.61 s81.1 mph138 bhp
Nissan Qashqai 2.0 dCi 150 (2010)20108.97 s16.59 s81.2 mph148 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 2010s4,541 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.0 178 0-60 time?
The Ssangyong Korando 2.0 178 reaches 60 mph in 8.96 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,364th quickest of the 14,946 cars in the set.
What is the Ssangyong Korando 2.0 178 quarter mile time?
16.65 s at 80.9 mph. It reaches the eighth mile in 10.56 s and clears the first 60 ft in 2.32 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ssangyong Korando 2.0 178 have?
176 bhp and 1,828 kg, which is 96 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ssangyong Korando 2.0 178?
Closest here on pace: Jeep Compass 1.4 MultiAir 140 (8.94 s), Vauxhall Mokka 1.4 Turbo 140 (8.97 s), Nissan Qashqai 2.0 dCi 150 (2010) (8.97 s). Each one can be raced against the Ssangyong Korando 2.0 178 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.0 178 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.