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

Kia Sportage 2.0 16V 141 (2004)

The Kia Sportage 2.0 16V 141 (2004) reaches 60 mph in 10.32 s (100 km/h in 10.90 s) and covers a standing quarter mile in 18.11 s, tripping the lights at 80.3 mph. It clears the first 60 ft in 3.21 s and the eighth mile in 11.95 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 16V 141 (2004) Infiniti QX4 3.3 V6 170

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 16V 141 (2004)
0–60 mph10.32 s
0–100 km/h10.90 s
0–100 mph—
60 ft3.21 s
1/8 mile11.95 s
1/4 mile18.11 s
Trap speed80.3 mph

About the Sportage 2.0 16V 141

The 2004 Kia Sportage 2.0 16V 141 (2004) is an all-wheel-drive naturally aspirated SUV of 1,525 kg with 139 bhp, which works out at 91 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.21 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 10,670th quickest to 60 mph, and the 108th quickest of the 205 Kias here. Its 80.3 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 16V 141 (2004)
Year2004
Power139 hp (104 kW)
Kerb mass1,525 kg
Power to weight91 bhp/t
DrivetrainAll-wheel drive
Gears4
EngineNaturally aspirated
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Infiniti QX4 3.3 V6 170199710.24 s18.04 s80.8 mph168 bhp
Nissan Juke 1.6i CVT 117201010.33 s17.78 s76.6 mph115 bhp
Subaru Forester 2.0 125200210.39 s17.87 s78.8 mph123 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
Kia 0-60 timesevery modelFastest SUVs2,049 carsFastest cars of the 2000s5,138 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 16V 141 (2004) 0-60 time?
The Kia Sportage 2.0 16V 141 (2004) reaches 60 mph in 10.32 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,670th quickest of the 14,946 cars in the set.
What is the Kia Sportage 2.0 16V 141 (2004) quarter mile time?
18.11 s at 80.3 mph. It reaches the eighth mile in 11.95 s and clears the first 60 ft in 3.21 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Sportage 2.0 16V 141 (2004) have?
139 bhp and 1,525 kg, which is 91 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 4 gears and a quoted top speed of 175 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Sportage 2.0 16V 141 (2004)?
Closest here on pace: Infiniti QX4 3.3 V6 170 (10.24 s), Nissan Juke 1.6i CVT 117 (10.33 s), Subaru Forester 2.0 125 (10.39 s). Each one can be raced against the Kia Sportage 2.0 16V 141 (2004) 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 16V 141 (2004) 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.