← My Auto Racer All cars Skoda 0-60 Comparisons
The Skoda Octavia RS 5E reaches 60 mph in 5.95 s and covers a standing quarter mile in 14.47 s, tripping the lights at 97.3 mph. It clears the first 60 ft in 2.32 s and the eighth mile in 9.38 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 | Skoda Octavia RS 5E |
|---|---|
| 0–60 mph | 5.95 s |
| 0–100 mph | — |
| 60 ft | 2.32 s |
| 1/8 mile | 9.38 s |
| 1/4 mile | 14.47 s |
| Trap speed | 97.3 mph |
The 2013 Skoda Octavia RS 5E is a front-drive turbocharged saloon of 1,350 kg with 217 bhp, which works out at 161 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.32 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,925th quickest to 60 mph, and the 5th quickest of the 22 Skodas here. Its 97.3 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 | Skoda Octavia RS 5E |
|---|---|
| Year | 2013 |
| Power | 217 bhp |
| Kerb mass | 1,350 kg |
| Power to weight | 161 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 246 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Saab 9-3 2.8T Turbo X Mk II | 2008 | 6.00 s | 14.55 s | 94.5 mph | 276 bhp |
| Smart #5 363 PS | 2025 | 5.99 s | 14.24 s | 105.6 mph | 358 bhp |
| Audi A3 3.2 quattro 8P | 2003 | 6.17 s | 14.53 s | 97.9 mph | 247 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.