← My Auto Racer All cars Ifr 0-60 Comparisons
The Ifr Aspid Super Sport reaches 60 mph in 2.90 s and covers a standing quarter mile in 10.34 s, tripping the lights at 138.9 mph. It clears the first 60 ft in 1.57 s and the eighth mile in 6.77 s, reaching 100 mph in 5.50 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 | Ifr Aspid Super Sport |
|---|---|
| 0–60 mph | 2.90 s |
| 0–100 mph | 5.50 s |
| 60 ft | 1.57 s |
| 1/8 mile | 6.77 s |
| 1/4 mile | 10.34 s |
| Trap speed | 138.9 mph |
The 2008 Ifr Aspid Super Sport is a rear-drive naturally aspirated supercar of 740 kg with 402 bhp, which works out at 544 bhp per tonne. Rear drive and 544 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.57 s. Against the 2,929 cars in the set it is the 186th quickest to 60 mph, inside the fastest tenth, and the 2nd quickest of the 2 Ifrs here. Its 138.9 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 5 of 5 published acceleration figures for this car.
| Specification | Ifr Aspid Super Sport |
|---|---|
| Year | 2008 |
| Power | 402 bhp |
| Kerb mass | 740 kg |
| Power to weight | 544 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Pagani Zonda Cinque | 2009 | 2.75 s | 10.45 s | 137.7 mph | 671 bhp |
| 9ff BT-2 | 2009 | 2.76 s | 10.31 s | 138.8 mph | 850 bhp |
| Noble M600 | 2009 | 3.00 s | 10.55 s | 138.7 mph | 650 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.