← My Auto Racer All cars Skoda 0-60 Comparisons
The Skoda Octavia RS Combi 5E reaches 60 mph in 5.76 s and covers a standing quarter mile in 14.30 s, tripping the lights at 98.2 mph. It clears the first 60 ft in 2.27 s and the eighth mile in 9.25 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 Combi 5E |
|---|---|
| 0–60 mph | 5.76 s |
| 0–100 mph | — |
| 60 ft | 2.27 s |
| 1/8 mile | 9.25 s |
| 1/4 mile | 14.30 s |
| Trap speed | 98.2 mph |
The 2013 Skoda Octavia RS Combi 5E is a front-drive turbocharged saloon of 1,387 kg with 217 bhp, which works out at 157 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.27 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,828th quickest to 60 mph, and the 3rd quickest of the 22 Skodas here. Its 98.2 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 Combi 5E |
|---|---|
| Year | 2013 |
| Power | 217 bhp |
| Kerb mass | 1,387 kg |
| Power to weight | 157 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 244 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Volvo S60 T6 | 2010 | 5.74 s | 14.21 s | 100.1 mph | 300 bhp |
| Audi A6 4.2 quattro | 2007 | 5.72 s | 14.26 s | 98.8 mph | 330 bhp |
| Acura TL | 2009 | 5.78 s | 14.35 s | 97.5 mph | 304 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.