← My Auto Racer All cars Monteverdi 0-60 Comparisons
The Monteverdi Hai 450 SS reaches 60 mph in 5.61 s and covers a standing quarter mile in 13.78 s, tripping the lights at 108.1 mph. It clears the first 60 ft in 2.45 s and the eighth mile in 9.14 s, reaching 100 mph in 12.01 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 | Monteverdi Hai 450 SS |
|---|---|
| 0–60 mph | 5.61 s |
| 0–100 mph | 12.01 s |
| 60 ft | 2.45 s |
| 1/8 mile | 9.14 s |
| 1/4 mile | 13.78 s |
| Trap speed | 108.1 mph |
The 1970 Monteverdi Hai 450 SS is a rear-drive naturally aspirated supercar of 1,247 kg with 425 bhp, which works out at 341 bhp per tonne. Rear drive and 341 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.45 s. Against the 2,929 cars in the set it is the 1,743rd quickest to 60 mph. It traps higher than its 0-60 suggests — 108.1 mph, the 1,126th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 8 of 10 published acceleration figures for this car.
| Specification | Monteverdi Hai 450 SS |
|---|---|
| Year | 1970 |
| Power | 425 bhp |
| Kerb mass | 1,247 kg |
| Power to weight | 341 bhp/t |
| Drivetrain | Rear drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 290 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lister Jaguar XJ-S 6.0 | 1983 | 5.52 s | 13.65 s | 110.0 mph | 475 bhp |
| Plymouth HEMI Cuda | 1970 | 5.60 s | 13.66 s | 109.2 mph | 425 bhp |
| Lotec 928 GT Kompressor | 1991 | 5.17 s | 13.22 s | 112.0 mph | 512 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.