← My Auto Racer All cars Volvo 0-60 Comparisons Answers
The Volvo XC40 D3 150 reaches 60 mph in 8.52 s and covers a standing quarter mile in 16.68 s, tripping the lights at 83.4 mph. It clears the first 60 ft in 2.58 s and the eighth mile in 10.79 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 XC40 D3 150 |
|---|---|
| 0–60 mph | 8.52 s |
| 0–100 mph | — |
| 60 ft | 2.58 s |
| 1/8 mile | 10.79 s |
| 1/4 mile | 16.68 s |
| Trap speed | 83.4 mph |
The 2018 Volvo XC40 D3 150 is a front-drive turbodiesel SUV of 1,575 kg with 148 bhp, which works out at 94 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.58 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,737th quickest to 60 mph, and the 24th quickest of the 27 Volvos here. Its 83.4 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 2 of 2 published acceleration figures for this car.
| Specification | Volvo XC40 D3 150 |
|---|---|
| Year | 2018 |
| Power | 148 bhp |
| Kerb mass | 1,575 kg |
| Power to weight | 94 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 200 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Renault Zoe R135 | 2019 | 8.52 s | 16.61 s | 82.0 mph | 134 bhp |
| Mazda CX-7 2.2 CD | 2009 | 8.57 s | 16.60 s | 81.3 mph | 170 bhp |
| Ford Focus 1.0 EcoBoost 125 (Mk4) | 2018 | 8.59 s | 16.70 s | 82.4 mph | 123 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.