← My Auto Racer All cars Mclaren 0-60 Comparisons
The Mclaren 788HS reaches 60 mph in 2.48 s and covers a standing quarter mile in 9.70 s, tripping the lights at 148.3 mph. It clears the first 60 ft in 1.63 s and the eighth mile in 6.37 s, reaching 100 mph in 4.69 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 | Mclaren 788HS |
|---|---|
| 0–60 mph | 2.48 s |
| 0–100 mph | 4.69 s |
| 60 ft | 1.63 s |
| 1/8 mile | 6.37 s |
| 1/4 mile | 9.70 s |
| Trap speed | 148.3 mph |
The 2026 Mclaren 788HS is a rear-drive turbocharged supercar of 1,389 kg with 778 bhp, which works out at 560 bhp per tonne. Rear drive and 560 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.63 s. Against the 2,929 cars in the set it is the 60th quickest to 60 mph, inside the fastest five per cent, and the 3rd quickest of the 30 Mclarens here. Its 148.3 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 | Mclaren 788HS |
|---|---|
| Year | 2026 |
| Power | 778 bhp |
| Kerb mass | 1,389 kg |
| Power to weight | 560 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 330 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ferrari 296 Speciale | 2025 | 2.51 s | 9.73 s | 147.7 mph | 868 bhp |
| Ferrari 296 Speciale A | 2026 | 2.51 s | 9.78 s | 146.3 mph | 868 bhp |
| Lamborghini Temerario | 2024 | 2.36 s | 9.74 s | 144.8 mph | 908 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.