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

Holden Jackaroo 5dr 3.0 DTI 160

The Holden Jackaroo 5dr 3.0 DTI 160 reaches 60 mph in 14.85 s (100 km/h in 15.99 s) and covers a standing quarter mile in 20.13 s, tripping the lights at 68.4 mph. It clears the first 60 ft in 3.23 s and the eighth mile in 12.93 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 Jackaroo 5dr 3.0 DTI 160 Subaru Justy 3dr 1.0 50

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 Jackaroo 5dr 3.0 DTI 160
0–60 mph14.85 s
0–100 km/h15.99 s
0–100 mph—
60 ft3.23 s
1/8 mile12.93 s
1/4 mile20.13 s
Trap speed68.4 mph

About the Jackaroo 5dr 3.0 DTI 160

The 1998 Holden Jackaroo 5dr 3.0 DTI 160 is an all-wheel-drive turbodiesel car of 2,170 kg with 157 bhp, which works out at 72 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.23 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 14,399th quickest to 60 mph, and the 109th quickest of the 110 Holdens here. Its 68.4 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 Holden Jackaroo 5dr 3.0 DTI 160
Year1998
Power157 hp (117 kW)
Kerb mass2,170 kg
Power to weight72 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed99 mph (160 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Subaru Justy 3dr 1.0 50198914.84 s20.04 s69.1 mph50 bhp
Subaru Justy 5dr 1.0 50198914.84 s20.04 s69.1 mph50 bhp
Lada Samara 3dr 1.3 65198614.57 s20.25 s70.8 mph64 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
Holden 0-60 timesevery modelFastest 4x4s and all-wheel-drive cars2,981 carsFastest cars of the 1990s2,649 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 Jackaroo 5dr 3.0 DTI 160 0-60 time?
The Holden Jackaroo 5dr 3.0 DTI 160 reaches 60 mph in 14.85 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,399th quickest of the 14,946 cars in the set.
What is the Holden Jackaroo 5dr 3.0 DTI 160 quarter mile time?
20.13 s at 68.4 mph. It reaches the eighth mile in 12.93 s and clears the first 60 ft in 3.23 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Holden Jackaroo 5dr 3.0 DTI 160 have?
157 bhp and 2,170 kg, which is 72 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 gears and a quoted top speed of 160 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Holden Jackaroo 5dr 3.0 DTI 160?
Closest here on pace: Subaru Justy 3dr 1.0 50 (14.84 s), Subaru Justy 5dr 1.0 50 (14.84 s), Lada Samara 3dr 1.3 65 (14.57 s). Each one can be raced against the Holden Jackaroo 5dr 3.0 DTI 160 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 Jackaroo 5dr 3.0 DTI 160 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.