← My Auto Racer All cars Ferrari 0-60 Comparisons
The Ferrari 296 Speciale reaches 60 mph in 2.51 s and covers a standing quarter mile in 9.73 s, tripping the lights at 147.7 mph. It clears the first 60 ft in 1.63 s and the eighth mile in 6.39 s, reaching 100 mph in 4.74 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 | Ferrari 296 Speciale |
|---|---|
| 0–60 mph | 2.51 s |
| 0–100 mph | 4.74 s |
| 60 ft | 1.63 s |
| 1/8 mile | 6.39 s |
| 1/4 mile | 9.73 s |
| Trap speed | 147.7 mph |
The 2025 Ferrari 296 Speciale is a rear-drive turbocharged supercar of 1,531 kg with 868 bhp, which works out at 567 bhp per tonne. Rear drive and 567 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 68th quickest to 60 mph, inside the fastest five per cent, and the 5th quickest of the 81 Ferraris here. Its 147.7 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 | Ferrari 296 Speciale |
|---|---|
| Year | 2025 |
| Power | 868 bhp |
| Kerb mass | 1,531 kg |
| Power to weight | 567 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 342 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mclaren 788HS | 2026 | 2.48 s | 9.70 s | 148.3 mph | 778 bhp |
| Mclaren 765LT Spider | 2021 | 2.51 s | 9.83 s | 145.2 mph | 755 bhp |
| Mclaren 750S | 2023 | 2.51 s | 9.87 s | 144.1 mph | 740 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.