← My Auto Racer All cars Peugeot 0-60 Comparisons
The Peugeot RCZ R reaches 60 mph in 5.26 s and covers a standing quarter mile in 13.69 s, tripping the lights at 103.8 mph. It clears the first 60 ft in 2.26 s and the eighth mile in 8.95 s, reaching 100 mph in 12.42 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 RCZ R |
|---|---|
| 0–60 mph | 5.26 s |
| 0–100 mph | 12.42 s |
| 60 ft | 2.26 s |
| 1/8 mile | 8.95 s |
| 1/4 mile | 13.69 s |
| Trap speed | 103.8 mph |
The 2013 Peugeot RCZ R is a front-drive turbocharged car of 1,280 kg with 267 bhp, which works out at 208 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.26 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,531st quickest to 60 mph, and the quickest of the 27 Peugeots here. Its 103.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 9 of 10 published acceleration figures for this car.
| Specification | Peugeot RCZ R |
|---|---|
| Year | 2013 |
| Power | 267 bhp |
| Kerb mass | 1,280 kg |
| Power to weight | 208 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| SEAT Leon Cupra 280 Mk III | 2014 | 5.32 s | 13.68 s | 105.1 mph | 276 bhp |
| Subaru WRX STI | 2018 | 5.27 s | 13.69 s | 101.6 mph | 304 bhp |
| SEAT Leon Cupra R Mk III | 2017 | 5.32 s | 13.60 s | 106.7 mph | 306 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.