← My Auto Racer All cars Hsv 0-60 Comparisons
The Hsv Coupe GTO VZ reaches 60 mph in 4.15 s and covers a standing quarter mile in 12.73 s, tripping the lights at 112.1 mph. It clears the first 60 ft in 2.02 s and the eighth mile in 8.24 s, reaching 100 mph in 10.39 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Hsv Coupe GTO VZ |
|---|---|
| 0–60 mph | 4.15 s |
| 0–100 mph | 10.39 s |
| 60 ft | 2.02 s |
| 1/8 mile | 8.24 s |
| 1/4 mile | 12.73 s |
| Trap speed | 112.1 mph |
The 2004 Hsv Coupe GTO VZ is a rear-drive naturally aspirated muscle car of 1,680 kg with 398 bhp, which works out at 237 bhp per tonne. Rear drive and 237 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.02 s. Against the 2,929 cars in the set it is the 877th quickest to 60 mph, and the quickest of the 2 Hsvs here. Its 112.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 5 of 7 published acceleration figures for this car.
| Specification | Hsv Coupe GTO VZ |
|---|---|
| Year | 2004 |
| Power | 398 bhp |
| Kerb mass | 1,680 kg |
| Power to weight | 237 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 290 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ford Mustang SVT Cobra R Mk IV 390 PS | 2000 | 4.13 s | 12.75 s | 111.8 mph | 385 bhp |
| Pontiac GTO 6.0 | 2006 | 4.21 s | 12.91 s | 110.0 mph | 394 bhp |
| Chevrolet Camaro SS Mk VI | 2016 | 4.10 s | 12.45 s | 114.9 mph | 447 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.