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

Kia Sportage 2.0 CRDi 140

The Kia Sportage 2.0 CRDi 140 reaches 60 mph in 10.04 s (100 km/h in 10.68 s) and covers a standing quarter mile in 17.38 s, tripping the lights at 77.5 mph. It clears the first 60 ft in 2.44 s and the eighth mile in 11.03 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 CRDi 140 Land Rover Discovery Sport 2.0 D150 5-Seat 150

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 CRDi 140
0–60 mph10.04 s
0–100 km/h10.68 s
0–100 mph—
60 ft2.44 s
1/8 mile11.03 s
1/4 mile17.38 s
Trap speed77.5 mph

About the Sportage 2.0 CRDi 140

The 2004 Kia Sportage 2.0 CRDi 140 is an all-wheel-drive turbodiesel SUV of 1,660 kg with 138 bhp, which works out at 83 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.44 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,243rd quickest to 60 mph, and the 94th quickest of the 205 Kias here. It leaves better than it pulls: 77.5 mph at the lights is only the 11,383rd 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 Kia Sportage 2.0 CRDi 140
Year2004
Power138 hp (103 kW)
Kerb mass1,660 kg
Power to weight83 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed110 mph (177 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Discovery Sport 2.0 D150 5-Seat 150201910.10 s17.35 s78.9 mph148 bhp
Chevrolet Captiva 2.2 DSL 163201110.07 s17.45 s77.3 mph161 bhp
Jeep Compass 2.0 CRD 140200710.01 s17.36 s79.1 mph134 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 CRDi 140 0-60 time?
The Kia Sportage 2.0 CRDi 140 reaches 60 mph in 10.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,243rd quickest of the 14,946 cars in the set.
What is the Kia Sportage 2.0 CRDi 140 quarter mile time?
17.38 s at 77.5 mph. It reaches the eighth mile in 11.03 s and clears the first 60 ft in 2.44 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Sportage 2.0 CRDi 140 have?
138 bhp and 1,660 kg, which is 83 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 177 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Sportage 2.0 CRDi 140?
Closest here on pace: Land Rover Discovery Sport 2.0 D150 5-Seat 150 (10.10 s), Chevrolet Captiva 2.2 DSL 163 (10.07 s), Jeep Compass 2.0 CRD 140 (10.01 s). Each one can be raced against the Kia Sportage 2.0 CRDi 140 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 CRDi 140 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.