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

Peugeot 206 SW 1.6 HDiF 110

The Peugeot 206 SW 1.6 HDiF 110 reaches 60 mph in 9.07 s (100 km/h in 9.61 s) and covers a standing quarter mile in 16.87 s, tripping the lights at 81.6 mph. It clears the first 60 ft in 2.65 s and the eighth mile in 10.83 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 206 SW 1.6 HDiF 110 Citroen Xsara Break 1.6i 110

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 206 SW 1.6 HDiF 110
0–60 mph9.07 s
0–100 km/h9.61 s
0–100 mph—
60 ft2.65 s
1/8 mile10.83 s
1/4 mile16.87 s
Trap speed81.6 mph

About the 206 SW 1.6 HDiF 110

The 2002 Peugeot 206 SW 1.6 HDiF 110 is a front-drive turbodiesel estate of 1,089 kg with 107 bhp, which works out at 99 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.65 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,545th quickest to 60 mph, and the 126th quickest of the 456 Peugeots here. Its 81.6 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 206 SW 1.6 HDiF 110
Year2002
Power107 hp (80 kW)
Kerb mass1,089 kg
Power to weight99 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Citroen Xsara Break 1.6i 11020009.02 s16.87 s83.7 mph107 bhp
Renault Laguna Estate 2.0 16V 14020019.02 s16.84 s84.6 mph138 bhp
Renault Talisman Estate 1.7 BluedCi 15020169.02 s16.94 s82.2 mph148 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 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 Peugeot 206 SW 1.6 HDiF 110 0-60 time?
The Peugeot 206 SW 1.6 HDiF 110 reaches 60 mph in 9.07 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,545th quickest of the 14,946 cars in the set.
What is the Peugeot 206 SW 1.6 HDiF 110 quarter mile time?
16.87 s at 81.6 mph. It reaches the eighth mile in 10.83 s and clears the first 60 ft in 2.65 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 206 SW 1.6 HDiF 110 have?
107 bhp and 1,089 kg, which is 99 bhp per tonne. It is front-drive, turbodiesel, with 5 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 Peugeot 206 SW 1.6 HDiF 110?
Closest here on pace: Citroen Xsara Break 1.6i 110 (9.02 s), Renault Laguna Estate 2.0 16V 140 (9.02 s), Renault Talisman Estate 1.7 BluedCi 150 (9.02 s). Each one can be raced against the Peugeot 206 SW 1.6 HDiF 110 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 206 SW 1.6 HDiF 110 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.