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

Subaru XV 2.0i CVT 147

The Subaru XV 2.0i CVT 147 reaches 60 mph in 7.51 s (100 km/h in 8.05 s) and covers a standing quarter mile in 15.92 s, tripping the lights at 84.7 mph. It clears the first 60 ft in 2.40 s and the eighth mile in 10.13 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.0i CVT 147 Audi Q3 Sportback 40 TDI 190

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.0i CVT 147
0–60 mph7.51 s
0–100 km/h8.05 s
0–100 mph—
60 ft2.40 s
1/8 mile10.13 s
1/4 mile15.92 s
Trap speed84.7 mph

About the XV 2.0i CVT 147

The 2012 Subaru XV 2.0i CVT 147 is an all-wheel-drive naturally aspirated SUV of 1,370 kg with 146 bhp, which works out at 107 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.40 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 5,581st quickest to 60 mph, and the 46th quickest of the 119 Subarus here. It leaves better than it pulls: 84.7 mph at the lights is only the 7,463rd 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.0i CVT 147
Year2012
Power146 hp (109 kW)
Kerb mass1,370 kg
Power to weight107 bhp/t
DrivetrainAll-wheel drive
Gears1
EngineNaturally aspirated
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Audi Q3 Sportback 40 TDI 19020197.50 s15.83 s89.4 mph188 bhp
VW Tiguan 2.0 TDI 4MOTION 17720117.55 s15.85 s84.0 mph174 bhp
VW Tiguan 2.0 TDI 4MOTION 17020117.55 s15.91 s84.6 mph168 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 8 seconds6,514 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.0i CVT 147 0-60 time?
The Subaru XV 2.0i CVT 147 reaches 60 mph in 7.51 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,581st quickest of the 14,946 cars in the set.
What is the Subaru XV 2.0i CVT 147 quarter mile time?
15.92 s at 84.7 mph. It reaches the eighth mile in 10.13 s and clears the first 60 ft in 2.40 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Subaru XV 2.0i CVT 147 have?
146 bhp and 1,370 kg, which is 107 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 1 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Subaru XV 2.0i CVT 147?
Closest here on pace: Audi Q3 Sportback 40 TDI 190 (7.50 s), VW Tiguan 2.0 TDI 4MOTION 177 (7.55 s), VW Tiguan 2.0 TDI 4MOTION 170 (7.55 s). Each one can be raced against the Subaru XV 2.0i CVT 147 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.0i CVT 147 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.