← My Auto Racer All cars Saab 0-60 Comparisons
The Saab 9-5 2.8T XWD reaches 60 mph in 6.37 s and covers a standing quarter mile in 14.84 s, tripping the lights at 94.5 mph. It clears the first 60 ft in 2.35 s and the eighth mile in 9.58 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 | Saab 9-5 2.8T XWD |
|---|---|
| 0–60 mph | 6.37 s |
| 0–100 mph | — |
| 60 ft | 2.35 s |
| 1/8 mile | 9.58 s |
| 1/4 mile | 14.84 s |
| Trap speed | 94.5 mph |
The 2010 Saab 9-5 2.8T XWD is an all-wheel-drive turbocharged saloon of 1,870 kg with 295 bhp, which works out at 158 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.35 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 2,929 cars in the set it is the 2,131st quickest to 60 mph, and the 4th quickest of the 6 Saabs here. Its 94.5 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 10 published acceleration figures for this car.
| Specification | Saab 9-5 2.8T XWD |
|---|---|
| Year | 2010 |
| Power | 295 bhp |
| Kerb mass | 1,870 kg |
| Power to weight | 158 bhp/t |
| Drivetrain | All-wheel drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 254 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Fisker Karma | 2010 | 6.41 s | 15.00 s | 91.7 mph | 402 bhp |
| Acura RL | 2009 | 6.57 s | 15.12 s | 93.1 mph | 300 bhp |
| Audi A3 3.2 quattro 8P | 2003 | 6.17 s | 14.53 s | 97.9 mph | 247 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.