← My Auto Racer All cars Pagani 0-60 Comparisons
The Pagani Huayra reaches 60 mph in 3.11 s and covers a standing quarter mile in 10.52 s, tripping the lights at 141.3 mph. It clears the first 60 ft in 1.74 s and the eighth mile in 6.94 s, reaching 100 mph in 5.91 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 | Pagani Huayra |
|---|---|
| 0–60 mph | 3.11 s |
| 0–100 mph | 5.91 s |
| 60 ft | 1.74 s |
| 1/8 mile | 6.94 s |
| 1/4 mile | 10.52 s |
| Trap speed | 141.3 mph |
The 2011 Pagani Huayra is a rear-drive turbocharged supercar of 1,350 kg with 720 bhp, which works out at 533 bhp per tonne. Rear drive and 533 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.74 s. Against the 2,929 cars in the set it is the 275th quickest to 60 mph, inside the fastest tenth, and the 3rd quickest of the 10 Paganis here. It traps higher than its 0-60 suggests — 141.3 mph, the 79th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 11 of 11 published acceleration figures for this car.
| Specification | Pagani Huayra |
|---|---|
| Year | 2011 |
| Power | 720 bhp |
| Kerb mass | 1,350 kg |
| Power to weight | 533 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 370 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Noble M600 | 2009 | 3.00 s | 10.55 s | 138.7 mph | 650 bhp |
| Ultima GTR 500 | 1999 | 3.22 s | 10.77 s | 138.7 mph | 557 bhp |
| Ruf CTR3 | 2008 | 2.95 s | 10.62 s | 135.3 mph | 691 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.