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

Pontiac Vibe GT 1.8 VVTL-i 175

The Pontiac Vibe GT 1.8 VVTL-i 175 reaches 60 mph in 7.73 s (100 km/h in 8.14 s) and covers a standing quarter mile in 16.07 s, tripping the lights at 87.4 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.45 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.

Pontiac Vibe GT 1.8 VVTL-i 175 Abarth 500c

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 Pontiac Vibe GT 1.8 VVTL-i 175
0–60 mph7.73 s
0–100 km/h8.14 s
0–100 mph—
60 ft2.55 s
1/8 mile10.45 s
1/4 mile16.07 s
Trap speed87.4 mph

About the Vibe GT 1.8 VVTL-i 175

The 2003 Pontiac Vibe GT 1.8 VVTL-i 175 is a front-drive naturally aspirated car of 1,270 kg with 173 bhp, which works out at 136 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 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 5,984th quickest to 60 mph, and the 16th quickest of the 26 Pontiacs here. Its 87.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 Pontiac Vibe GT 1.8 VVTL-i 175
Year2003
Power173 hp (129 kW)
Kerb mass1,270 kg
Power to weight136 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Abarth 500c20107.72 s16.10 s85.3 mph138 bhp
Fiat Strada 130TC Abarth19837.77 s15.95 s87.6 mph129 bhp
Honda Prelude 2.0 e:HEV 203 PS20257.81 s16.01 s87.1 mph200 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 8 seconds6,514 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
Pontiac 0-60 timesevery modelFastest hatchbacks4,513 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 Pontiac Vibe GT 1.8 VVTL-i 175 0-60 time?
The Pontiac Vibe GT 1.8 VVTL-i 175 reaches 60 mph in 7.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,984th quickest of the 14,946 cars in the set.
What is the Pontiac Vibe GT 1.8 VVTL-i 175 quarter mile time?
16.07 s at 87.4 mph. It reaches the eighth mile in 10.45 s and clears the first 60 ft in 2.55 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Pontiac Vibe GT 1.8 VVTL-i 175 have?
173 bhp and 1,270 kg, which is 136 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Pontiac Vibe GT 1.8 VVTL-i 175?
Closest here on pace: Abarth 500c (7.72 s), Fiat Strada 130TC Abarth (7.77 s), Honda Prelude 2.0 e:HEV 203 PS (7.81 s). Each one can be raced against the Pontiac Vibe GT 1.8 VVTL-i 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 Pontiac Vibe GT 1.8 VVTL-i 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.