← My Auto Racer All cars Pontiac 0-60 Comparisons
The Pontiac GTO 6.0 reaches 60 mph in 4.21 s and covers a standing quarter mile in 12.91 s, tripping the lights at 110.0 mph. It clears the first 60 ft in 2.01 s and the eighth mile in 8.35 s, reaching 100 mph in 10.82 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 | Pontiac GTO 6.0 |
|---|---|
| 0–60 mph | 4.21 s |
| 0–100 mph | 10.82 s |
| 60 ft | 2.01 s |
| 1/8 mile | 8.35 s |
| 1/4 mile | 12.91 s |
| Trap speed | 110.0 mph |
The 2006 Pontiac GTO 6.0 is a rear-drive naturally aspirated muscle car of 1,668 kg with 394 bhp, which works out at 236 bhp per tonne. Rear drive and 236 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.01 s. Against the 2,929 cars in the set it is the 919th quickest to 60 mph, and the quickest of the 11 Pontiacs here. Its 110.0 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 4 of 7 published acceleration figures for this car.
| Specification | Pontiac GTO 6.0 |
|---|---|
| Year | 2006 |
| Power | 394 bhp |
| Kerb mass | 1,668 kg |
| Power to weight | 236 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 274 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Hsv Coupe GTO VZ | 2004 | 4.15 s | 12.73 s | 112.1 mph | 398 bhp |
| Ford Mustang SVT Cobra R Mk IV 390 PS | 2000 | 4.13 s | 12.75 s | 111.8 mph | 385 bhp |
| Dodge Challenger SRT-8 392 | 2011 | 4.45 s | 12.98 s | 111.7 mph | 471 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.