← My Auto Racer All cars Mclaren 0-60 Comparisons
The Mclaren W1 reaches 60 mph in 2.43 s and covers a standing quarter mile in 9.12 s, tripping the lights at 166.8 mph. It clears the first 60 ft in 1.61 s and the eighth mile in 6.13 s, reaching 100 mph in 4.22 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 W1 |
|---|---|
| 0–60 mph | 2.43 s |
| 0–100 mph | 4.22 s |
| 60 ft | 1.61 s |
| 1/8 mile | 6.13 s |
| 1/4 mile | 9.12 s |
| Trap speed | 166.8 mph |
The 2025 Mclaren W1 is a rear-drive turbocharged supercar of 1,587 kg with 1,258 bhp, which works out at 793 bhp per tonne. Rear drive and 793 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.61 s. Against the 2,929 cars in the set it is the 54th quickest to 60 mph, inside the fastest five per cent, and the 2nd quickest of the 30 Mclarens here. Its 166.8 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 W1 |
|---|---|
| Year | 2025 |
| Power | 1,258 bhp |
| Kerb mass | 1,587 kg |
| Power to weight | 793 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 350 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Audi R10 TDI | 2006 | 2.32 s | 9.32 s | 158.5 mph | 650 bhp |
| Bugatti Centodieci | 2019 | 2.08 s | 9.17 s | 155.7 mph | 1,578 bhp |
| Isotta Fraschini Tipo 6 LMH Strada | 2024 | 2.49 s | 9.26 s | 167.0 mph | 966 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.