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

Peugeot 308 SW 1.6 THP 175

The Peugeot 308 SW 1.6 THP 175 reaches 60 mph in 8.14 s (100 km/h in 8.63 s) and covers a standing quarter mile in 16.32 s, tripping the lights at 86.0 mph. It clears the first 60 ft in 2.50 s and the eighth mile in 10.52 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 308 SW 1.6 THP 175 Renault Talisman Estate 1.3 TCe 160

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 308 SW 1.6 THP 175
0–60 mph8.14 s
0–100 km/h8.63 s
0–100 mph—
60 ft2.50 s
1/8 mile10.52 s
1/4 mile16.32 s
Trap speed86.0 mph

About the 308 SW 1.6 THP 175

The 2008 Peugeot 308 SW 1.6 THP 175 is a front-drive turbocharged estate of 1,524 kg with 172 bhp, which works out at 113 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.50 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 6,791st quickest to 60 mph, and the 68th quickest of the 456 Peugeots here. Its 86.0 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 308 SW 1.6 THP 175
Year2008
Power172 hp (128 kW)
Kerb mass1,524 kg
Power to weight113 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed133 mph (214 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Talisman Estate 1.3 TCe 16020168.19 s16.37 s84.1 mph158 bhp
Citroen XM Break 3.0 V6 19419978.13 s16.41 s89.6 mph192 bhp
VW Passat Variant 2.0 TDI B6 170 PS20058.20 s16.41 s87.0 mph168 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 308 SW 1.6 THP 175 0-60 time?
The Peugeot 308 SW 1.6 THP 175 reaches 60 mph in 8.14 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,791st quickest of the 14,946 cars in the set.
What is the Peugeot 308 SW 1.6 THP 175 quarter mile time?
16.32 s at 86.0 mph. It reaches the eighth mile in 10.52 s and clears the first 60 ft in 2.50 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 308 SW 1.6 THP 175 have?
172 bhp and 1,524 kg, which is 113 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 214 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 308 SW 1.6 THP 175?
Closest here on pace: Renault Talisman Estate 1.3 TCe 160 (8.19 s), Citroen XM Break 3.0 V6 194 (8.13 s), VW Passat Variant 2.0 TDI B6 170 PS (8.20 s). Each one can be raced against the Peugeot 308 SW 1.6 THP 175 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 308 SW 1.6 THP 175 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.