← My Auto Racer All cars Peugeot 0-60 Comparisons
The Peugeot 208 GTI 200 PS reaches 60 mph in 5.80 s and covers a standing quarter mile in 14.46 s, tripping the lights at 94.4 mph. It clears the first 60 ft in 2.21 s and the eighth mile in 9.27 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Peugeot 208 GTI 200 PS |
|---|---|
| 0–60 mph | 5.80 s |
| 0–100 mph | — |
| 60 ft | 2.21 s |
| 1/8 mile | 9.27 s |
| 1/4 mile | 14.46 s |
| Trap speed | 94.4 mph |
The 2012 Peugeot 208 GTI 200 PS is a front-drive turbocharged car of 1,160 kg with 197 bhp, which works out at 170 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.21 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 1,850th quickest to 60 mph, and the 4th quickest of the 27 Peugeots here. It leaves better than it pulls: 94.4 mph at the lights is only the 2,190th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Peugeot 208 GTI 200 PS |
|---|---|
| Year | 2012 |
| Power | 197 bhp |
| Kerb mass | 1,160 kg |
| Power to weight | 170 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 230 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| SEAT Leon Cupra | 2006 | 5.82 s | 14.36 s | 97.5 mph | 237 bhp |
| Ford Focus ST | 2012 | 5.84 s | 14.36 s | 98.2 mph | 247 bhp |
| Acura TSX V-6 | 2010 | 5.71 s | 14.34 s | 97.8 mph | 280 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.