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

Hyundai Ioniq 1.6 Plug-In 139

The Hyundai Ioniq 1.6 Plug-In 139 reaches 60 mph in 10.02 s (100 km/h in 10.68 s) and covers a standing quarter mile in 17.53 s, tripping the lights at 78.9 mph. It clears the first 60 ft in 2.81 s and the eighth mile in 11.30 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 Ioniq 1.6 Plug-In 139 Vauxhall Insignia Sedan 2.0 CDTI ecoFLEX 130

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 Ioniq 1.6 Plug-In 139
0–60 mph10.02 s
0–100 km/h10.68 s
0–100 mph—
60 ft2.81 s
1/8 mile11.30 s
1/4 mile17.53 s
Trap speed78.9 mph

About the Ioniq 1.6 Plug-In 139

The 2016 Hyundai Ioniq 1.6 Plug-In 139 is a front-drive naturally aspirated saloon of 1,370 kg with 105 bhp, which works out at 76 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.81 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,178th quickest to 60 mph, and the 135th quickest of the 295 Hyundais here. Its 78.9 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 Ioniq 1.6 Plug-In 139
Year2016
Power105 hp (78 kW)
Kerb mass1,370 kg
Power to weight76 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Vauxhall Insignia Sedan 2.0 CDTI ecoFLEX 130200810.01 s17.55 s79.4 mph129 bhp
Skoda Superb 1.6 TDI 12020209.97 s17.48 s79.0 mph118 bhp
Holden Vectra 1.9 CDTI 12020029.93 s17.51 s79.3 mph118 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 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 Hyundai Ioniq 1.6 Plug-In 139 0-60 time?
The Hyundai Ioniq 1.6 Plug-In 139 reaches 60 mph in 10.02 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,178th quickest of the 14,946 cars in the set.
What is the Hyundai Ioniq 1.6 Plug-In 139 quarter mile time?
17.53 s at 78.9 mph. It reaches the eighth mile in 11.30 s and clears the first 60 ft in 2.81 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Ioniq 1.6 Plug-In 139 have?
105 bhp and 1,370 kg, which is 76 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Ioniq 1.6 Plug-In 139?
Closest here on pace: Vauxhall Insignia Sedan 2.0 CDTI ecoFLEX 130 (10.01 s), Skoda Superb 1.6 TDI 120 (9.97 s), Holden Vectra 1.9 CDTI 120 (9.93 s). Each one can be raced against the Hyundai Ioniq 1.6 Plug-In 139 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 Ioniq 1.6 Plug-In 139 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.