← My Auto Racer All cars Maserati 0-60 Comparisons
The Maserati MC20 reaches 60 mph in 2.63 s and covers a standing quarter mile in 10.48 s, tripping the lights at 133.0 mph. It clears the first 60 ft in 1.65 s and the eighth mile in 6.77 s, reaching 100 mph in 5.88 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 | Maserati MC20 |
|---|---|
| 0–60 mph | 2.63 s |
| 0–100 mph | 5.88 s |
| 60 ft | 1.65 s |
| 1/8 mile | 6.77 s |
| 1/4 mile | 10.48 s |
| Trap speed | 133.0 mph |
The 2021 Maserati MC20 is a rear-drive turbocharged supercar of 1,500 kg with 621 bhp, which works out at 414 bhp per tonne. Rear drive and 414 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.65 s. Against the 2,929 cars in the set it is the 104th quickest to 60 mph, inside the fastest five per cent, and the 2nd quickest of the 37 Maseratis here. Its 133.0 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 | Maserati MC20 |
|---|---|
| Year | 2021 |
| Power | 621 bhp |
| Kerb mass | 1,500 kg |
| Power to weight | 414 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 328 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mclaren 570S | 2016 | 2.65 s | 10.48 s | 133.8 mph | 562 bhp |
| Zeekr 9X | 2025 | 2.61 s | 10.46 s | 133.9 mph | 1,381 bhp |
| Lamborghini Aventador LP700-4 | 2011 | 2.72 s | 10.48 s | 137.1 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.