← My Auto Racer All cars Subaru 0-60 Comparisons Answers

Subaru XV 2.0D 145

The Subaru XV 2.0D 145 reaches 60 mph in 8.42 s (100 km/h in 8.92 s) and covers a standing quarter mile in 16.23 s, tripping the lights at 83.0 mph. It clears the first 60 ft in 2.26 s and the eighth mile in 10.30 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.

Subaru XV 2.0D 145 MINI Countryman Cooper SD ALL 4 2.0 143

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Subaru XV 2.0D 145
0–60 mph8.42 s
0–100 km/h8.92 s
0–100 mph—
60 ft2.26 s
1/8 mile10.30 s
1/4 mile16.23 s
Trap speed83.0 mph

About the XV 2.0D 145

The 2012 Subaru XV 2.0D 145 is an all-wheel-drive turbodiesel SUV of 1,435 kg with 145 bhp, which works out at 101 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.26 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 7,342nd quickest to 60 mph, and the 62nd quickest of the 119 Subarus here. It leaves better than it pulls: 83.0 mph at the lights is only the 8,361st highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Subaru XV 2.0D 145
Year2012
Power145 hp (108 kW)
Kerb mass1,435 kg
Power to weight101 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed120 mph (193 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
MINI Countryman Cooper SD ALL 4 2.0 14320148.43 s16.20 s83.1 mph141 bhp
MINI Countryman Cooper SD ALL4 2.0 143 (2014)20148.45 s16.38 s82.3 mph141 bhp
Vauxhall Mokka X 1.4i ecoTEC 14020168.41 s16.42 s84.1 mph138 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.

Where these times sit

0-60 under 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Subaru 0-60 timesevery modelFastest SUVs2,049 carsFastest cars of the 2010s4,541 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Subaru XV 2.0D 145 0-60 time?
The Subaru XV 2.0D 145 reaches 60 mph in 8.42 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,342nd quickest of the 14,946 cars in the set.
What is the Subaru XV 2.0D 145 quarter mile time?
16.23 s at 83.0 mph. It reaches the eighth mile in 10.30 s and clears the first 60 ft in 2.26 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Subaru XV 2.0D 145 have?
145 bhp and 1,435 kg, which is 101 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 193 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Subaru XV 2.0D 145?
Closest here on pace: MINI Countryman Cooper SD ALL 4 2.0 143 (8.43 s), MINI Countryman Cooper SD ALL4 2.0 143 (2014) (8.45 s), Vauxhall Mokka X 1.4i ecoTEC 140 (8.41 s). Each one can be raced against the Subaru XV 2.0D 145 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Subaru XV 2.0D 145 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.