← My Auto Racer All cars Pontiac 0-60 Comparisons Answers
The Pontiac Firebird 3.4 V6 reaches 60 mph in 9.88 s and covers a standing quarter mile in 17.46 s, tripping the lights at 83.8 mph. It clears the first 60 ft in 3.08 s and the eighth mile in 11.57 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 Firebird 3.4 V6 |
|---|---|
| 0–60 mph | 9.88 s |
| 0–100 mph | — |
| 60 ft | 3.08 s |
| 1/8 mile | 11.57 s |
| 1/4 mile | 17.46 s |
| Trap speed | 83.8 mph |
The 1994 Pontiac Firebird 3.4 V6 is a rear-drive naturally aspirated muscle car of 1,553 kg with 146 bhp, which works out at 94 bhp per tonne. Rear drive and 94 bhp per tonne make the launch the hard part of the run: 60 ft takes 3.08 s. Against the 2,939 cars in the set it is the 2,865th quickest to 60 mph, and the 11th quickest of the 11 Pontiacs here. Its 83.8 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 7 of 9 published acceleration figures for this car.
| Specification | Pontiac Firebird 3.4 V6 |
|---|---|
| Year | 1994 |
| Power | 146 bhp |
| Kerb mass | 1,553 kg |
| Power to weight | 94 bhp/t |
| Drivetrain | Rear drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 207 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Honda Civic 1.0 VTEC Turbo (FK) | 2017 | 9.82 s | 17.45 s | 79.9 mph | 127 bhp |
| Seat Ibiza 1.0 TSI 95 (Mk5) | 2017 | 9.87 s | 17.43 s | 78.8 mph | 94 bhp |
| Volkswagen Polo 1.0 TSI 95 | 2022 | 9.92 s | 17.45 s | 78.8 mph | 94 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.