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

Hyundai Kona 1.6 CRDi 136

The Hyundai Kona 1.6 CRDi 136 reaches 60 mph in 10.04 s (100 km/h in 10.75 s) and covers a standing quarter mile in 17.33 s, tripping the lights at 77.2 mph. It clears the first 60 ft in 2.43 s and the eighth mile in 10.95 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 Kona 1.6 CRDi 136 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 Kona 1.6 CRDi 136
0–60 mph10.04 s
0–100 km/h10.75 s
0–100 mph—
60 ft2.43 s
1/8 mile10.95 s
1/4 mile17.33 s
Trap speed77.2 mph

About the Kona 1.6 CRDi 136

The 2017 Hyundai Kona 1.6 CRDi 136 is an all-wheel-drive turbodiesel car of 1,497 kg with 134 bhp, which works out at 90 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.43 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 10,257th quickest to 60 mph, and the 141st quickest of the 295 Hyundais here. It leaves better than it pulls: 77.2 mph at the lights is only the 11,569th 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 Hyundai Kona 1.6 CRDi 136
Year2017
Power134 hp (100 kW)
Kerb mass1,497 kg
Power to weight90 bhp/t
DrivetrainAll-wheel drive
Gears7
EngineTurbodiesel
Top speed116 mph (187 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
Nissan Note 1.5 dCI 106200810.08 s17.46 s78.4 mph105 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 4x4s and all-wheel-drive cars2,981 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 Kona 1.6 CRDi 136 0-60 time?
The Hyundai Kona 1.6 CRDi 136 reaches 60 mph in 10.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,257th quickest of the 14,946 cars in the set.
What is the Hyundai Kona 1.6 CRDi 136 quarter mile time?
17.33 s at 77.2 mph. It reaches the eighth mile in 10.95 s and clears the first 60 ft in 2.43 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Kona 1.6 CRDi 136 have?
134 bhp and 1,497 kg, which is 90 bhp per tonne. It is all-wheel-drive, turbodiesel, with 7 gears and a quoted top speed of 187 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Kona 1.6 CRDi 136?
Closest here on pace: Vauxhall Corsa 3dr 1.4 Turbo 100 (9.99 s), Vauxhall Corsa 5dr 1.4 Turbo 100 (9.99 s), Nissan Note 1.5 dCI 106 (10.08 s). Each one can be raced against the Hyundai Kona 1.6 CRDi 136 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 Kona 1.6 CRDi 136 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.