← My Auto Racer All cars Panoz 0-60 Comparisons
The Panoz Esperante reaches 60 mph in 4.93 s and covers a standing quarter mile in 13.31 s, tripping the lights at 103.9 mph. It clears the first 60 ft in 2.03 s and the eighth mile in 8.60 s, reaching 100 mph in 11.76 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 | Panoz Esperante |
|---|---|
| 0–60 mph | 4.93 s |
| 0–100 mph | 11.76 s |
| 60 ft | 2.03 s |
| 1/8 mile | 8.60 s |
| 1/4 mile | 13.31 s |
| Trap speed | 103.9 mph |
The 2004 Panoz Esperante is a rear-drive naturally aspirated car of 1,451 kg with 315 bhp, which works out at 217 bhp per tonne. Rear drive and 217 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.03 s. Against the 2,929 cars in the set it is the 1,349th quickest to 60 mph, and the 3rd quickest of the 3 Panozs here. Its 103.9 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 7 published acceleration figures for this car.
| Specification | Panoz Esperante |
|---|---|
| Year | 2004 |
| Power | 315 bhp |
| Kerb mass | 1,451 kg |
| Power to weight | 217 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 252 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Subaru Impreza Turbo STI PPP | 2002 | 4.92 s | 13.43 s | 101.8 mph | 300 bhp |
| MG X-Power SV | 2015 | 4.85 s | 13.31 s | 106.8 mph | 315 bhp |
| Venturi 260 LM | 1993 | 4.85 s | 13.38 s | 104.9 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.