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

Holden Vectra Liftback 2.0 DTi 101

The Holden Vectra Liftback 2.0 DTi 101 reaches 60 mph in 11.83 s (100 km/h in 12.55 s) and covers a standing quarter mile in 18.53 s, tripping the lights at 76.1 mph. It clears the first 60 ft in 3.08 s and the eighth mile in 12.01 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 Vectra Liftback 2.0 DTi 101 SEAT Toledo 1.9 TDI 90 (1999)

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 Vectra Liftback 2.0 DTi 101
0–60 mph11.83 s
0–100 km/h12.55 s
0–100 mph—
60 ft3.08 s
1/8 mile12.01 s
1/4 mile18.53 s
Trap speed76.1 mph

About the Vectra Liftback 2.0 DTi 101

The 1996 Holden Vectra Liftback 2.0 DTi 101 is a front-drive turbodiesel car of 1,450 kg with 99 bhp, which works out at 68 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.08 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 12,654th quickest to 60 mph, and the 88th quickest of the 110 Holdens here. Its 76.1 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 Vectra Liftback 2.0 DTi 101
Year1996
Power99 hp (74 kW)
Kerb mass1,450 kg
Power to weight68 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
SEAT Toledo 1.9 TDI 90 (1999)199911.78 s18.56 s74.3 mph89 bhp
Dacia 1310 Break 1.6 72199411.85 s18.49 s74.0 mph71 bhp
Lada Kalina Hatchback 1.4 TDI 70200711.71 s18.54 s73.7 mph70 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 diesel cars4,019 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 Vectra Liftback 2.0 DTi 101 0-60 time?
The Holden Vectra Liftback 2.0 DTi 101 reaches 60 mph in 11.83 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,654th quickest of the 14,946 cars in the set.
What is the Holden Vectra Liftback 2.0 DTi 101 quarter mile time?
18.53 s at 76.1 mph. It reaches the eighth mile in 12.01 s and clears the first 60 ft in 3.08 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Holden Vectra Liftback 2.0 DTi 101 have?
99 bhp and 1,450 kg, which is 68 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Holden Vectra Liftback 2.0 DTi 101?
Closest here on pace: SEAT Toledo 1.9 TDI 90 (1999) (11.78 s), Dacia 1310 Break 1.6 72 (11.85 s), Lada Kalina Hatchback 1.4 TDI 70 (11.71 s). Each one can be raced against the Holden Vectra Liftback 2.0 DTi 101 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 Vectra Liftback 2.0 DTi 101 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.