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

Kia Sportage 2.0 GDI 166

The Kia Sportage 2.0 GDI 166 reaches 60 mph in 9.92 s (100 km/h in 10.58 s) and covers a standing quarter mile in 17.47 s, tripping the lights at 78.6 mph. It clears the first 60 ft in 2.75 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.

Kia Sportage 2.0 GDI 166 Mazda CX-5 2.0 Skyactiv-G 155

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 Kia Sportage 2.0 GDI 166
0–60 mph9.92 s
0–100 km/h10.58 s
0–100 mph—
60 ft2.75 s
1/8 mile11.21 s
1/4 mile17.47 s
Trap speed78.6 mph

About the Sportage 2.0 GDI 166

The 2013 Kia Sportage 2.0 GDI 166 is an all-wheel-drive naturally aspirated SUV of 1,544 kg with 164 bhp, which works out at 106 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.75 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 9,982nd quickest to 60 mph, and the 90th quickest of the 205 Kias here. Its 78.6 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 Kia Sportage 2.0 GDI 166
Year2013
Power164 hp (122 kW)
Kerb mass1,544 kg
Power to weight106 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda CX-5 2.0 Skyactiv-G 15520169.92 s17.47 s79.3 mph153 bhp
Jeep Renegade 1.4 MultiAir 14020149.92 s17.44 s78.3 mph138 bhp
Suzuki Escudo / Grand Vitara 5dr 2.5 V6 14419989.91 s17.59 s79.4 mph142 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 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Kia 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 Kia Sportage 2.0 GDI 166 0-60 time?
The Kia Sportage 2.0 GDI 166 reaches 60 mph in 9.92 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,982nd quickest of the 14,946 cars in the set.
What is the Kia Sportage 2.0 GDI 166 quarter mile time?
17.47 s at 78.6 mph. It reaches the eighth mile in 11.21 s and clears the first 60 ft in 2.75 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Sportage 2.0 GDI 166 have?
164 bhp and 1,544 kg, which is 106 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 6 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Sportage 2.0 GDI 166?
Closest here on pace: Mazda CX-5 2.0 Skyactiv-G 155 (9.92 s), Jeep Renegade 1.4 MultiAir 140 (9.92 s), Suzuki Escudo / Grand Vitara 5dr 2.5 V6 144 (9.91 s). Each one can be raced against the Kia Sportage 2.0 GDI 166 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 Kia Sportage 2.0 GDI 166 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.