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

Peugeot 405 Break 1.9 125

The Peugeot 405 Break 1.9 125 reaches 60 mph in 9.30 s (100 km/h in 9.82 s) and covers a standing quarter mile in 17.07 s, tripping the lights at 82.8 mph. It clears the first 60 ft in 2.90 s and the eighth mile in 11.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.

Peugeot 405 Break 1.9 125 Mitsubishi Lancer Combi 1.6i 114

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 Peugeot 405 Break 1.9 125
0–60 mph9.30 s
0–100 km/h9.82 s
0–100 mph—
60 ft2.90 s
1/8 mile11.13 s
1/4 mile17.07 s
Trap speed82.8 mph

About the 405 Break 1.9 125

The 1988 Peugeot 405 Break 1.9 125 is a front-drive naturally aspirated estate of 1,064 kg with 123 bhp, which works out at 116 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.90 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 8,948th quickest to 60 mph, and the 145th quickest of the 456 Peugeots here. Its 82.8 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 Peugeot 405 Break 1.9 125
Year1988
Power123 hp (92 kW)
Kerb mass1,064 kg
Power to weight116 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Lancer Combi 1.6i 11419929.29 s17.12 s82.0 mph111 bhp
Mazda 6/Atenza Wagon 2.3 16V 166 (2005)20059.17 s17.10 s83.6 mph164 bhp
Mazda 6/Atenza Wagon 2.0 16V 12720079.28 s17.16 s83.0 mph145 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
Peugeot 0-60 timesevery modelFastest estate cars1,484 carsFastest cars of the 1980s1,057 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 Peugeot 405 Break 1.9 125 0-60 time?
The Peugeot 405 Break 1.9 125 reaches 60 mph in 9.30 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,948th quickest of the 14,946 cars in the set.
What is the Peugeot 405 Break 1.9 125 quarter mile time?
17.07 s at 82.8 mph. It reaches the eighth mile in 11.13 s and clears the first 60 ft in 2.90 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 405 Break 1.9 125 have?
123 bhp and 1,064 kg, which is 116 bhp per tonne. It is front-drive, naturally aspirated, with 5 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 Peugeot 405 Break 1.9 125?
Closest here on pace: Mitsubishi Lancer Combi 1.6i 114 (9.29 s), Mazda 6/Atenza Wagon 2.3 16V 166 (2005) (9.17 s), Mazda 6/Atenza Wagon 2.0 16V 127 (9.28 s). Each one can be raced against the Peugeot 405 Break 1.9 125 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 Peugeot 405 Break 1.9 125 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.