← My Auto Racer All cars Pontiac 0-60 Comparisons
The Pontiac Solstice GXP reaches 60 mph in 5.03 s and covers a standing quarter mile in 13.73 s, tripping the lights at 99.8 mph. It clears the first 60 ft in 2.10 s and the eighth mile in 8.81 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 Solstice GXP |
|---|---|
| 0–60 mph | 5.03 s |
| 0–100 mph | — |
| 60 ft | 2.10 s |
| 1/8 mile | 8.81 s |
| 1/4 mile | 13.73 s |
| Trap speed | 99.8 mph |
The 2006 Pontiac Solstice GXP is a rear-drive turbocharged car of 1,337 kg with 260 bhp, which works out at 195 bhp per tonne. Rear drive and 195 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.10 s. Against the 2,929 cars in the set it is the 1,408th quickest to 60 mph, and the 5th quickest of the 11 Pontiacs here. It leaves better than it pulls: 99.8 mph at the lights is only the 1,751st highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 7 of 7 published acceleration figures for this car.
| Specification | Pontiac Solstice GXP |
|---|---|
| Year | 2006 |
| Power | 260 bhp |
| Kerb mass | 1,337 kg |
| Power to weight | 195 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 229 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Opel Insignia OPC Mk I | 2009 | 5.14 s | 13.74 s | 100.4 mph | 321 bhp |
| Buick GranSport Stage 1 GS 455 | 1970 | 4.97 s | 13.67 s | 104.4 mph | 359 bhp |
| Saturn Sky Red Line | 2007 | 5.14 s | 13.89 s | 97.5 mph | 260 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.