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

Subaru Impreza Wagon 1.6 95 (2000)

The Subaru Impreza Wagon 1.6 95 (2000) reaches 60 mph in 14.73 s (100 km/h in 15.92 s) and covers a standing quarter mile in 20.81 s, tripping the lights at 71.4 mph. It clears the first 60 ft in 3.75 s and the eighth mile in 13.88 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 Impreza Wagon 1.6 95 (2000) Dodge Aries Coupe 2.2 84

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 Impreza Wagon 1.6 95 (2000)
0–60 mph14.73 s
0–100 km/h15.92 s
0–100 mph—
60 ft3.75 s
1/8 mile13.88 s
1/4 mile20.81 s
Trap speed71.4 mph

About the Impreza Wagon 1.6 95

The 2000 Subaru Impreza Wagon 1.6 95 (2000) is a front-drive naturally aspirated estate of 1,275 kg with 94 bhp, which works out at 74 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.75 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 14,359th quickest to 60 mph, and the 113th quickest of the 119 Subarus here. Its 71.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.

On paper

Specification Subaru Impreza Wagon 1.6 95 (2000)
Year2000
Power94 hp (70 kW)
Kerb mass1,275 kg
Power to weight74 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed102 mph (164 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Aries Coupe 2.2 84198114.71 s20.84 s72.9 mph84 bhp
Dacia 1310 Break 1.4 65198415.00 s20.44 s69.7 mph64 bhp
Toyota Corolla 3dr 1.3 86199714.86 s21.03 s74.2 mph84 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Subaru 0-60 timesevery modelFastest estate cars1,484 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 Impreza Wagon 1.6 95 (2000) 0-60 time?
The Subaru Impreza Wagon 1.6 95 (2000) reaches 60 mph in 14.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,359th quickest of the 14,946 cars in the set.
What is the Subaru Impreza Wagon 1.6 95 (2000) quarter mile time?
20.81 s at 71.4 mph. It reaches the eighth mile in 13.88 s and clears the first 60 ft in 3.75 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Subaru Impreza Wagon 1.6 95 (2000) have?
94 bhp and 1,275 kg, which is 74 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 164 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Subaru Impreza Wagon 1.6 95 (2000)?
Closest here on pace: Dodge Aries Coupe 2.2 84 (14.71 s), Dacia 1310 Break 1.4 65 (15.00 s), Toyota Corolla 3dr 1.3 86 (14.86 s). Each one can be raced against the Subaru Impreza Wagon 1.6 95 (2000) 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 Impreza Wagon 1.6 95 (2000) 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.