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

Hyundai ix20 1.6 125 (2015)

The Hyundai ix20 1.6 125 (2015) reaches 60 mph in 9.75 s (100 km/h in 10.39 s) and covers a standing quarter mile in 17.38 s, tripping the lights at 79.6 mph. It clears the first 60 ft in 2.78 s and the eighth mile in 11.20 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 ix20 1.6 125 (2015) Jeep Compass 2.4 170

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 ix20 1.6 125 (2015)
0–60 mph9.75 s
0–100 km/h10.39 s
0–100 mph—
60 ft2.78 s
1/8 mile11.20 s
1/4 mile17.38 s
Trap speed79.6 mph

About the ix20 1.6 125

The 2015 Hyundai ix20 1.6 125 (2015) is a front-drive naturally aspirated SUV of 1,180 kg with 123 bhp, which works out at 105 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.78 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,711th quickest to 60 mph, and the 121st quickest of the 295 Hyundais here. Its 79.6 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 ix20 1.6 125 (2015)
Year2015
Power123 hp (92 kW)
Kerb mass1,180 kg
Power to weight105 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Jeep Compass 2.4 17020119.74 s17.45 s80.3 mph168 bhp
Toyota RAV4 5dr 2.0 VVT-i 15220069.66 s17.36 s81.0 mph150 bhp
Jeep Compass 2.0 156 (2007)20079.66 s17.36 s81.0 mph154 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.

Head to head

Hyundai i20 1.0 120 vs Hyundai ix20 1.6 125 (2015)Full comparison

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
Hyundai 0-60 timesevery modelFastest SUVs2,049 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 ix20 1.6 125 (2015) 0-60 time?
The Hyundai ix20 1.6 125 (2015) reaches 60 mph in 9.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,711th quickest of the 14,946 cars in the set.
What is the Hyundai ix20 1.6 125 (2015) quarter mile time?
17.38 s at 79.6 mph. It reaches the eighth mile in 11.20 s and clears the first 60 ft in 2.78 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai ix20 1.6 125 (2015) have?
123 bhp and 1,180 kg, which is 105 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 ix20 1.6 125 (2015)?
Closest here on pace: Jeep Compass 2.4 170 (9.74 s), Toyota RAV4 5dr 2.0 VVT-i 152 (9.66 s), Jeep Compass 2.0 156 (2007) (9.66 s). Each one can be raced against the Hyundai ix20 1.6 125 (2015) 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 ix20 1.6 125 (2015) 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.