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

Holden Vectra 2.0 Turbo 175

The Holden Vectra 2.0 Turbo 175 reaches 60 mph in 8.25 s (100 km/h in 8.73 s) and covers a standing quarter mile in 16.32 s, tripping the lights at 86.4 mph. It clears the first 60 ft in 2.53 s and the eighth mile in 10.52 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 2.0 Turbo 175 Honda Civic Sedan 1.6i 110

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 2.0 Turbo 175
0–60 mph8.25 s
0–100 km/h8.73 s
0–100 mph—
60 ft2.53 s
1/8 mile10.52 s
1/4 mile16.32 s
Trap speed86.4 mph

About the Vectra 2.0 Turbo 175

The 2002 Holden Vectra 2.0 Turbo 175 is a front-drive turbocharged saloon of 1,485 kg with 173 bhp, which works out at 116 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.53 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 7,017th quickest to 60 mph, and the 35th quickest of the 110 Holdens here. Its 86.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 Vectra 2.0 Turbo 175
Year2002
Power173 hp (129 kW)
Kerb mass1,485 kg
Power to weight116 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed143 mph (230 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Honda Civic Sedan 1.6i 11019878.28 s16.41 s85.3 mph109 bhp
Opel Kadett Sedan 2.0i 11619858.19 s16.28 s86.6 mph114 bhp
Genesis G70 Shooting Brake 2.0 T-GDi 19720218.33 s16.34 s83.2 mph194 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 cars0-100 km/h under 10 seconds9,062 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 saloon cars3,808 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 Vectra 2.0 Turbo 175 0-60 time?
The Holden Vectra 2.0 Turbo 175 reaches 60 mph in 8.25 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,017th quickest of the 14,946 cars in the set.
What is the Holden Vectra 2.0 Turbo 175 quarter mile time?
16.32 s at 86.4 mph. It reaches the eighth mile in 10.52 s and clears the first 60 ft in 2.53 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Holden Vectra 2.0 Turbo 175 have?
173 bhp and 1,485 kg, which is 116 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 230 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Holden Vectra 2.0 Turbo 175?
Closest here on pace: Honda Civic Sedan 1.6i 110 (8.28 s), Opel Kadett Sedan 2.0i 116 (8.19 s), Genesis G70 Shooting Brake 2.0 T-GDi 197 (8.33 s). Each one can be raced against the Holden Vectra 2.0 Turbo 175 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 2.0 Turbo 175 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.