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

Subaru Outback 2.5 156

The Subaru Outback 2.5 156 reaches 60 mph in 9.73 s (100 km/h in 10.23 s) and covers a standing quarter mile in 17.61 s, tripping the lights at 84.2 mph. It clears the first 60 ft in 3.12 s and the eighth mile in 11.74 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 Outback 2.5 156 Chevrolet Malibu 2.4 169

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 Outback 2.5 156
0–60 mph9.73 s
0–100 km/h10.23 s
0–100 mph—
60 ft3.12 s
1/8 mile11.74 s
1/4 mile17.61 s
Trap speed84.2 mph

About the Outback 2.5 156

The 2002 Subaru Outback 2.5 156 is an all-wheel-drive naturally aspirated saloon of 1,445 kg with 154 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 3.12 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 9,657th quickest to 60 mph, and the 82nd quickest of the 119 Subarus here. It traps higher than its 0-60 suggests — 84.2 mph, the 7,676th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Subaru Outback 2.5 156
Year2002
Power154 hp (115 kW)
Kerb mass1,445 kg
Power to weight107 bhp/t
DrivetrainAll-wheel drive
Gears4
EngineNaturally aspirated
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Malibu 2.4 16920089.72 s17.63 s83.7 mph169 bhp
Mitsubishi Sigma 3.0 V6 17019919.85 s17.63 s86.7 mph168 bhp
Toyota Camry 2.4 VVT-i 15220019.64 s17.53 s85.1 mph150 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 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 4x4s and all-wheel-drive cars2,981 carsFastest cars of the 2000s5,138 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 Outback 2.5 156 0-60 time?
The Subaru Outback 2.5 156 reaches 60 mph in 9.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,657th quickest of the 14,946 cars in the set.
What is the Subaru Outback 2.5 156 quarter mile time?
17.61 s at 84.2 mph. It reaches the eighth mile in 11.74 s and clears the first 60 ft in 3.12 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Subaru Outback 2.5 156 have?
154 bhp and 1,445 kg, which is 107 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 4 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Subaru Outback 2.5 156?
Closest here on pace: Chevrolet Malibu 2.4 169 (9.72 s), Mitsubishi Sigma 3.0 V6 170 (9.85 s), Toyota Camry 2.4 VVT-i 152 (9.64 s). Each one can be raced against the Subaru Outback 2.5 156 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 Outback 2.5 156 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.