← My Auto Racer All cars Mclaren 0-60 Comparisons
The Mclaren MCL39 reaches 60 mph in 2.22 s and covers a standing quarter mile in 8.63 s, tripping the lights at 179.3 mph. It clears the first 60 ft in 1.54 s and the eighth mile in 5.85 s, reaching 100 mph in 3.87 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 MCL39 |
|---|---|
| 0–60 mph | 2.22 s |
| 0–100 mph | 3.87 s |
| 60 ft | 1.54 s |
| 1/8 mile | 5.85 s |
| 1/4 mile | 8.63 s |
| Trap speed | 179.3 mph |
The 2025 Mclaren MCL39 is a rear-drive turbocharged supercar of 800 kg with 1,035 bhp, which works out at 1,294 bhp per tonne. Rear drive and 1,294 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.54 s. Against the 2,929 cars in the set it is the 33rd quickest to 60 mph, inside the fastest five per cent, and the quickest of the 30 Mclarens here. Its 179.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 9 of 11 published acceleration figures for this car.
| Specification | Mclaren MCL39 |
|---|---|
| Year | 2025 |
| Power | 1,035 bhp |
| Kerb mass | 800 kg |
| Power to weight | 1,294 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 353 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mercedes-Benz W17 | 2026 | 2.41 s | 8.83 s | 181.7 mph | 1,038 bhp |
| Lotus Evija | 2019 | 2.12 s | 8.44 s | 186.2 mph | 2,012 bhp |
| Porsche 917/10 Spyder | 1971 | 1.82 s | 8.70 s | 170.9 mph | 1,000 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.