← My Auto Racer All cars Hennessey 0-60 Comparisons
The Hennessey Venom GT reaches 60 mph in 2.54 s and covers a standing quarter mile in 9.71 s, tripping the lights at 164.6 mph. It clears the first 60 ft in 1.70 s and the eighth mile in 6.59 s, reaching 100 mph in 5.33 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 | Hennessey Venom GT |
|---|---|
| 0–60 mph | 2.54 s |
| 0–100 mph | 5.33 s |
| 60 ft | 1.70 s |
| 1/8 mile | 6.59 s |
| 1/4 mile | 9.71 s |
| Trap speed | 164.6 mph |
The 2010 Hennessey Venom GT is a rear-drive turbocharged supercar of 1,220 kg with 1,200 bhp, which works out at 984 bhp per tonne. Rear drive and 984 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.70 s. Against the 2,929 cars in the set it is the 75th quickest to 60 mph, inside the fastest five per cent. Its 164.6 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 10 of 11 published acceleration figures for this car.
| Specification | Hennessey Venom GT |
|---|---|
| Year | 2010 |
| Power | 1,200 bhp |
| Kerb mass | 1,220 kg |
| Power to weight | 984 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 435 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Koenigsegg One:1 | 2014 | 2.65 s | 9.82 s | 166.3 mph | 1,340 bhp |
| 9ff GT9 Vmax | 2013 | 2.64 s | 9.82 s | 166.4 mph | 1,381 bhp |
| Koenigsegg Regera | 2016 | 2.56 s | 9.42 s | 162.1 mph | 1,479 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.