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

Hyundai i30 2.0 16V 143

The Hyundai i30 2.0 16V 143 reaches 60 mph in 9.67 s (100 km/h in 10.22 s) and covers a standing quarter mile in 17.30 s, tripping the lights at 82.6 mph. It clears the first 60 ft in 3.00 s and the eighth mile in 11.35 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 2.0 16V 143 Mitsubishi Galant 2000 GTi-16V Catalyst (144 PS) Pre Facelift

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 2.0 16V 143
0–60 mph9.67 s
0–100 km/h10.22 s
0–100 mph—
60 ft3.00 s
1/8 mile11.35 s
1/4 mile17.30 s
Trap speed82.6 mph

About the i30 2.0 16V 143

The 2007 Hyundai i30 2.0 16V 143 is a front-drive naturally aspirated car of 1,227 kg with 141 bhp, which works out at 115 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.00 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,596th quickest to 60 mph, and the 112th quickest of the 295 Hyundais here. It traps higher than its 0-60 suggests — 82.6 mph, the 8,577th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Hyundai i30 2.0 16V 143
Year2007
Power141 hp (105 kW)
Kerb mass1,227 kg
Power to weight115 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed127 mph (205 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Galant 2000 GTi-16V Catalyst (144 PS) Pre Facelift19889.70 s17.35 s82.8 mph142 bhp
Citroen C3 1.6 110 (2002)20029.66 s17.34 s81.6 mph109 bhp
Fiat 500 1.4 10020079.56 s17.32 s80.9 mph99 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 hatchbacks4,513 carsFastest cars of the 2000s5,138 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 2.0 16V 143 0-60 time?
The Hyundai i30 2.0 16V 143 reaches 60 mph in 9.67 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,596th quickest of the 14,946 cars in the set.
What is the Hyundai i30 2.0 16V 143 quarter mile time?
17.30 s at 82.6 mph. It reaches the eighth mile in 11.35 s and clears the first 60 ft in 3.00 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai i30 2.0 16V 143 have?
141 bhp and 1,227 kg, which is 115 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 205 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai i30 2.0 16V 143?
Closest here on pace: Mitsubishi Galant 2000 GTi-16V Catalyst (144 PS) Pre Facelift (9.70 s), Citroen C3 1.6 110 (2002) (9.66 s), Fiat 500 1.4 100 (9.56 s). Each one can be raced against the Hyundai i30 2.0 16V 143 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 2.0 16V 143 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.