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

Hyundai i30 1.6 CRDi 110 (Mk3)

The Hyundai i30 1.6 CRDi 110 (Mk3) reaches 60 mph in 10.00 s (100 km/h in 10.59 s) and covers a standing quarter mile in 17.33 s, tripping the lights at 79.0 mph. It clears the first 60 ft in 2.59 s and the eighth mile in 11.12 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.

Hyundai i30 1.6 CRDi 110 (Mk3) Vauxhall Corsa 3dr 1.4 Turbo 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 Hyundai i30 1.6 CRDi 110 (Mk3)
0–60 mph10.00 s
0–100 km/h10.59 s
0–100 mph—
60 ft2.59 s
1/8 mile11.12 s
1/4 mile17.33 s
Trap speed79.0 mph

About the i30 1.6 CRDi 110 (Mk3)

The 2017 Hyundai i30 1.6 CRDi 110 (Mk3) is a front-drive turbodiesel car of 1,263 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.59 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 10,150th quickest to 60 mph, and the 132nd quickest of the 295 Hyundais here. Its 79.0 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 Hyundai i30 1.6 CRDi 110 (Mk3)
Year2017
Power109 hp (81 kW)
Kerb mass1,263 kg
Power to weight86 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Vauxhall Corsa 3dr 1.4 Turbo 10020149.99 s17.36 s78.8 mph99 bhp
Vauxhall Corsa 5dr 1.4 Turbo 10020149.99 s17.36 s78.8 mph99 bhp
Mazda 626 (Mk.5) Hatchback 2.0 DiTD 11019979.98 s17.44 s78.9 mph109 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Hyundai 0-60 timesevery modelFastest diesel cars4,019 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 Hyundai i30 1.6 CRDi 110 (Mk3) 0-60 time?
The Hyundai i30 1.6 CRDi 110 (Mk3) reaches 60 mph in 10.00 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,150th quickest of the 14,946 cars in the set.
What is the Hyundai i30 1.6 CRDi 110 (Mk3) quarter mile time?
17.33 s at 79.0 mph. It reaches the eighth mile in 11.12 s and clears the first 60 ft in 2.59 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai i30 1.6 CRDi 110 (Mk3) have?
109 bhp and 1,263 kg, which is 86 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai i30 1.6 CRDi 110 (Mk3)?
Closest here on pace: Vauxhall Corsa 3dr 1.4 Turbo 100 (9.99 s), Vauxhall Corsa 5dr 1.4 Turbo 100 (9.99 s), Mazda 626 (Mk.5) Hatchback 2.0 DiTD 110 (9.98 s). Each one can be raced against the Hyundai i30 1.6 CRDi 110 (Mk3) 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 Hyundai i30 1.6 CRDi 110 (Mk3) 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.