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

Subaru Forester 2.0 X 128

The Subaru Forester 2.0 X 128 reaches 60 mph in 8.83 s (100 km/h in 9.33 s) and covers a standing quarter mile in 16.78 s, tripping the lights at 83.5 mph. It clears the first 60 ft in 2.79 s and the eighth mile in 10.87 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 Forester 2.0 X 128 Porsche Cayenne (955) 3.2 V6 250

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 Forester 2.0 X 128
0–60 mph8.83 s
0–100 km/h9.33 s
0–100 mph—
60 ft2.79 s
1/8 mile10.87 s
1/4 mile16.78 s
Trap speed83.5 mph

About the Forester 2.0 X 128

The 2005 Subaru Forester 2.0 X 128 is an all-wheel-drive naturally aspirated SUV of 1,390 kg with 156 bhp, which works out at 112 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.79 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 8,088th quickest to 60 mph, and the 69th quickest of the 119 Subarus here. Its 83.5 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.

On paper

Specification Subaru Forester 2.0 X 128
Year2005
Power156 hp (116 kW)
Kerb mass1,390 kg
Power to weight112 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed117 mph (188 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Porsche Cayenne (955) 3.2 V6 25020028.78 s16.82 s84.2 mph247 bhp
Renault Koleos 2.5 CVT 17520168.80 s16.79 s81.7 mph173 bhp
Peugeot 5008 1.6 THP 15620098.84 s16.78 s81.7 mph154 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 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 Forester 2.0 X 128 0-60 time?
The Subaru Forester 2.0 X 128 reaches 60 mph in 8.83 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,088th quickest of the 14,946 cars in the set.
What is the Subaru Forester 2.0 X 128 quarter mile time?
16.78 s at 83.5 mph. It reaches the eighth mile in 10.87 s and clears the first 60 ft in 2.79 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Subaru Forester 2.0 X 128 have?
156 bhp and 1,390 kg, which is 112 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 5 gears and a quoted top speed of 188 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Subaru Forester 2.0 X 128?
Closest here on pace: Porsche Cayenne (955) 3.2 V6 250 (8.78 s), Renault Koleos 2.5 CVT 175 (8.80 s), Peugeot 5008 1.6 THP 156 (8.84 s). Each one can be raced against the Subaru Forester 2.0 X 128 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 Forester 2.0 X 128 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.