← My Auto Racer All cars Kia 0-60 Comparisons
The Kia Borrego V8 reaches 60 mph in 6.84 s and covers a standing quarter mile in 15.21 s, tripping the lights at 91.9 mph. It clears the first 60 ft in 2.37 s and the eighth mile in 9.81 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Kia Borrego V8 |
|---|---|
| 0–60 mph | 6.84 s |
| 0–100 mph | — |
| 60 ft | 2.37 s |
| 1/8 mile | 9.81 s |
| 1/4 mile | 15.21 s |
| Trap speed | 91.9 mph |
The 2009 Kia Borrego V8 is an all-wheel-drive naturally aspirated SUV of 2,091 kg with 337 bhp, which works out at 161 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.37 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 2,929 cars in the set it is the 2,327th quickest to 60 mph, and the 8th quickest of the 16 Kias here. Its 91.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 9 of 9 published acceleration figures for this car.
| Specification | Kia Borrego V8 |
|---|---|
| Year | 2009 |
| Power | 337 bhp |
| Kerb mass | 2,091 kg |
| Power to weight | 161 bhp/t |
| Drivetrain | All-wheel drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 193 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Land Rover LR4 | 2009 | 6.83 s | 15.33 s | 92.9 mph | 370 bhp |
| GMC Envoy Denali | 2009 | 6.85 s | 15.28 s | 92.8 mph | 300 bhp |
| Acura RDX SH-AWD | 2013 | 6.64 s | 15.15 s | 93.8 mph | 274 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.