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

Hyundai i40 Tourer 2.0 GDI 177

The Hyundai i40 Tourer 2.0 GDI 177 reaches 60 mph in 9.78 s (100 km/h in 10.38 s) and covers a standing quarter mile in 17.52 s, tripping the lights at 81.0 mph. It clears the first 60 ft in 2.93 s and the eighth mile in 11.37 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 i40 Tourer 2.0 GDI 177 Citroen XM Break 3.0 V6 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 i40 Tourer 2.0 GDI 177
0–60 mph9.78 s
0–100 km/h10.38 s
0–100 mph—
60 ft2.93 s
1/8 mile11.37 s
1/4 mile17.52 s
Trap speed81.0 mph

About the i40 Tourer 2.0 GDI 177

The 2012 Hyundai i40 Tourer 2.0 GDI 177 is a front-drive naturally aspirated estate of 1,574 kg with 174 bhp, which works out at 111 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.93 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,747th quickest to 60 mph, and the 124th quickest of the 295 Hyundais here. Its 81.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 i40 Tourer 2.0 GDI 177
Year2012
Power174 hp (130 kW)
Kerb mass1,574 kg
Power to weight111 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed129 mph (208 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Citroen XM Break 3.0 V6 17019949.78 s17.70 s83.5 mph168 bhp
Kia cee'd Sport Wagon 2.0 16V 14320079.82 s17.68 s84.0 mph141 bhp
Lancia Kappa SW 2.4 17519969.84 s17.66 s85.2 mph173 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
Hyundai 0-60 timesevery modelFastest estate cars1,484 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 i40 Tourer 2.0 GDI 177 0-60 time?
The Hyundai i40 Tourer 2.0 GDI 177 reaches 60 mph in 9.78 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,747th quickest of the 14,946 cars in the set.
What is the Hyundai i40 Tourer 2.0 GDI 177 quarter mile time?
17.52 s at 81.0 mph. It reaches the eighth mile in 11.37 s and clears the first 60 ft in 2.93 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai i40 Tourer 2.0 GDI 177 have?
174 bhp and 1,574 kg, which is 111 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 208 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai i40 Tourer 2.0 GDI 177?
Closest here on pace: Citroen XM Break 3.0 V6 170 (9.78 s), Kia cee'd Sport Wagon 2.0 16V 143 (9.82 s), Lancia Kappa SW 2.4 175 (9.84 s). Each one can be raced against the Hyundai i40 Tourer 2.0 GDI 177 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 i40 Tourer 2.0 GDI 177 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.