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

Holden Captiva 2.0 D 152

The Holden Captiva 2.0 D 152 reaches 60 mph in 9.56 s (100 km/h in 10.19 s) and covers a standing quarter mile in 17.26 s, tripping the lights at 78.9 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 11.00 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.

Holden Captiva 2.0 D 152 Land Rover Range Rover 4.0 V8 190

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 Holden Captiva 2.0 D 152
0–60 mph9.56 s
0–100 km/h10.19 s
0–100 mph—
60 ft2.62 s
1/8 mile11.00 s
1/4 mile17.26 s
Trap speed78.9 mph

About the Captiva 2.0 D 152

The 2006 Holden Captiva 2.0 D 152 is an all-wheel-drive turbodiesel SUV of 1,573 kg with 150 bhp, which works out at 95 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.62 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,390th quickest to 60 mph, and the 57th quickest of the 110 Holdens here. It leaves better than it pulls: 78.9 mph at the lights is only the 10,622nd 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 Holden Captiva 2.0 D 152
Year2006
Power150 hp (112 kW)
Kerb mass1,573 kg
Power to weight95 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Range Rover 4.0 V8 19019949.57 s17.28 s81.7 mph188 bhp
Vauxhall Antara 2.4 ECOTEC 16720109.56 s17.13 s81.2 mph165 bhp
Suzuki SX4 Sedan 1.6 CVT 11220069.61 s17.33 s78.7 mph113 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
Holden 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 Holden Captiva 2.0 D 152 0-60 time?
The Holden Captiva 2.0 D 152 reaches 60 mph in 9.56 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,390th quickest of the 14,946 cars in the set.
What is the Holden Captiva 2.0 D 152 quarter mile time?
17.26 s at 78.9 mph. It reaches the eighth mile in 11.00 s and clears the first 60 ft in 2.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Holden Captiva 2.0 D 152 have?
150 bhp and 1,573 kg, which is 95 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 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 Holden Captiva 2.0 D 152?
Closest here on pace: Land Rover Range Rover 4.0 V8 190 (9.57 s), Vauxhall Antara 2.4 ECOTEC 167 (9.56 s), Suzuki SX4 Sedan 1.6 CVT 112 (9.61 s). Each one can be raced against the Holden Captiva 2.0 D 152 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 Holden Captiva 2.0 D 152 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.