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

Skoda Octavia 1.4 G-TEC 110

The Skoda Octavia 1.4 G-TEC 110 reaches 60 mph in 9.73 s (100 km/h in 10.57 s) and covers a standing quarter mile in 17.33 s, tripping the lights at 78.9 mph. It clears the first 60 ft in 2.61 s and the eighth mile in 11.07 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.4 G-TEC 110 Mazda 3 / Axela Sedan 1.5 SKYACTIV-G 100

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.4 G-TEC 110
0–60 mph9.73 s
0–100 km/h10.57 s
0–100 mph—
60 ft2.61 s
1/8 mile11.07 s
1/4 mile17.33 s
Trap speed78.9 mph

About the Octavia 1.4 G-TEC 110

The 2017 Skoda Octavia 1.4 G-TEC 110 is a front-drive turbocharged saloon of 1,332 kg with 109 bhp, which works out at 82 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.61 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,666th quickest to 60 mph, and the 77th quickest of the 178 Skodas here. It leaves better than it pulls: 78.9 mph at the lights is only the 10,626th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Skoda Octavia 1.4 G-TEC 110
Year2017
Power109 hp (81 kW)
Kerb mass1,332 kg
Power to weight82 bhp/t
DrivetrainFront drive
Gears7
EngineTurbocharged
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda 3 / Axela Sedan 1.5 SKYACTIV-G 10020139.73 s17.26 s80.2 mph99 bhp
Hyundai Ioniq 1.6 14120169.74 s17.37 s79.5 mph105 bhp
Hyundai Ioniq 1.6 10520209.74 s17.37 s79.5 mph103 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.4 G-TEC 110 0-60 time?
The Skoda Octavia 1.4 G-TEC 110 reaches 60 mph in 9.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,666th quickest of the 14,946 cars in the set.
What is the Skoda Octavia 1.4 G-TEC 110 quarter mile time?
17.33 s at 78.9 mph. It reaches the eighth mile in 11.07 s and clears the first 60 ft in 2.61 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Skoda Octavia 1.4 G-TEC 110 have?
109 bhp and 1,332 kg, which is 82 bhp per tonne. It is front-drive, turbocharged, with 7 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Skoda Octavia 1.4 G-TEC 110?
Closest here on pace: Mazda 3 / Axela Sedan 1.5 SKYACTIV-G 100 (9.73 s), Hyundai Ioniq 1.6 141 (9.74 s), Hyundai Ioniq 1.6 105 (9.74 s). Each one can be raced against the Skoda Octavia 1.4 G-TEC 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.4 G-TEC 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.