← My Auto Racer All cars Panoz 0-60 Comparisons
The Panoz Esperante GTLM reaches 60 mph in 3.81 s and covers a standing quarter mile in 12.38 s, tripping the lights at 114.4 mph. It clears the first 60 ft in 1.92 s and the eighth mile in 7.99 s, reaching 100 mph in 9.70 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 GTLM |
|---|---|
| 0–60 mph | 3.81 s |
| 0–100 mph | 9.70 s |
| 60 ft | 1.92 s |
| 1/8 mile | 7.99 s |
| 1/4 mile | 12.38 s |
| Trap speed | 114.4 mph |
The 2006 Panoz Esperante GTLM is a rear-drive naturally aspirated car of 1,432 kg with 414 bhp, which works out at 289 bhp per tonne. Rear drive and 289 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.92 s. Against the 2,929 cars in the set it is the 689th quickest to 60 mph, inside the fastest quarter, and the quickest of the 3 Panozs here. Its 114.4 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 5 published acceleration figures for this car.
| Specification | Panoz Esperante GTLM |
|---|---|
| Year | 2006 |
| Power | 414 bhp |
| Kerb mass | 1,432 kg |
| Power to weight | 289 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 290 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lotus Evora 400 | 2016 | 3.96 s | 12.33 s | 115.0 mph | 400 bhp |
| Vector M12 | 1996 | 3.95 s | 12.25 s | 118.7 mph | 485 bhp |
| Alpine A110 S Mk II 300 PS | 2022 | 3.71 s | 12.21 s | 113.3 mph | 296 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.