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

Skoda Octavia 1.0 TSI EVO 110

The Skoda Octavia 1.0 TSI EVO 110 reaches 60 mph in 9.56 s (100 km/h in 10.19 s) and covers a standing quarter mile in 17.28 s, tripping the lights at 80.7 mph. It clears the first 60 ft in 2.63 s and the eighth mile in 11.09 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.

Skoda Octavia 1.0 TSI EVO 110 BMW 3 Series (E90) 318d 122

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 Skoda Octavia 1.0 TSI EVO 110
0–60 mph9.56 s
0–100 km/h10.19 s
0–100 mph—
60 ft2.63 s
1/8 mile11.09 s
1/4 mile17.28 s
Trap speed80.7 mph

About the Octavia 1.0 TSI EVO 110

The 2019 Skoda Octavia 1.0 TSI EVO 110 is a front-drive turbocharged saloon of 1,259 kg with 109 bhp, which works out at 86 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.63 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 9,387th quickest to 60 mph, and the 70th quickest of the 178 Skodas here. Its 80.7 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 Skoda Octavia 1.0 TSI EVO 110
Year2019
Power109 hp (81 kW)
Kerb mass1,259 kg
Power to weight86 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed129 mph (208 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
BMW 3 Series (E90) 318d 12220059.55 s17.26 s80.6 mph121 bhp
Renault Vel Satis 2.2 dCi 14020059.57 s17.30 s80.3 mph137 bhp
Chrysler Sebring Sedan 2.0 14120039.58 s17.25 s82.5 mph139 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 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Skoda 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 2010s4,541 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 Skoda Octavia 1.0 TSI EVO 110 0-60 time?
The Skoda Octavia 1.0 TSI EVO 110 reaches 60 mph in 9.56 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,387th quickest of the 14,946 cars in the set.
What is the Skoda Octavia 1.0 TSI EVO 110 quarter mile time?
17.28 s at 80.7 mph. It reaches the eighth mile in 11.09 s and clears the first 60 ft in 2.63 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Skoda Octavia 1.0 TSI EVO 110 have?
109 bhp and 1,259 kg, which is 86 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 208 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Skoda Octavia 1.0 TSI EVO 110?
Closest here on pace: BMW 3 Series (E90) 318d 122 (9.55 s), Renault Vel Satis 2.2 dCi 140 (9.57 s), Chrysler Sebring Sedan 2.0 141 (9.58 s). Each one can be raced against the Skoda Octavia 1.0 TSI EVO 110 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 Skoda Octavia 1.0 TSI EVO 110 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.