← My Auto Racer All cars Volvo 0-60 Comparisons Answers
The Volvo S90 D4 reaches 60 mph in 7.45 s and covers a standing quarter mile in 15.70 s, tripping the lights at 93.7 mph. It clears the first 60 ft in 2.72 s and the eighth mile in 10.42 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 | Volvo S90 D4 |
|---|---|
| 0–60 mph | 7.45 s |
| 0–100 mph | — |
| 60 ft | 2.72 s |
| 1/8 mile | 10.42 s |
| 1/4 mile | 15.70 s |
| Trap speed | 93.7 mph |
The 2016 Volvo S90 D4 is a front-drive turbodiesel saloon of 1,733 kg with 188 bhp, which works out at 108 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.72 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,509th quickest to 60 mph, and the 21st quickest of the 27 Volvos here. It traps higher than its 0-60 suggests — 93.7 mph, the 2,253rd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 10 of 10 published acceleration figures for this car.
| Specification | Volvo S90 D4 |
|---|---|
| Year | 2016 |
| Power | 188 bhp |
| Kerb mass | 1,733 kg |
| Power to weight | 108 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 230 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Audi A6 2.0 TDI 190 (C7) | 2014 | 7.40 s | 15.73 s | 90.0 mph | 188 bhp |
| VW Phaeton 3.0 TDI | 2008 | 7.51 s | 15.80 s | 87.6 mph | 237 bhp |
| MINI Cooper SD | 2011 | 7.44 s | 15.83 s | 87.2 mph | 141 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.