← My Auto Racer All cars Saleen 0-60 Comparisons
The Saleen SR reaches 60 mph in 3.77 s and covers a standing quarter mile in 11.89 s, tripping the lights at 122.6 mph. It clears the first 60 ft in 1.96 s and the eighth mile in 7.78 s, reaching 100 mph in 8.51 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 | Saleen SR |
|---|---|
| 0–60 mph | 3.77 s |
| 0–100 mph | 8.51 s |
| 60 ft | 1.96 s |
| 1/8 mile | 7.78 s |
| 1/4 mile | 11.89 s |
| Trap speed | 122.6 mph |
The 2001 Saleen SR is a rear-drive naturally aspirated supercar of 1,409 kg with 498 bhp, which works out at 353 bhp per tonne. Rear drive and 353 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.96 s. Against the 2,929 cars in the set it is the 661st quickest to 60 mph, inside the fastest quarter, and the 3rd quickest of the 4 Saleens here. It traps higher than its 0-60 suggests — 122.6 mph, the 416th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 5 of 5 published acceleration figures for this car.
| Specification | Saleen SR |
|---|---|
| Year | 2001 |
| Power | 498 bhp |
| Kerb mass | 1,409 kg |
| Power to weight | 353 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 326 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lexus LFA | 2010 | 3.77 s | 11.78 s | 125.4 mph | 553 bhp |
| Aston Martin Vanquish | 2014 | 3.65 s | 11.90 s | 120.8 mph | 569 bhp |
| Cadillac CTS-V Mk III | 2014 | 3.68 s | 11.70 s | 125.3 mph | 640 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.