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

Hyundai ix35 / Tucson 1.6 GDI 135

The Hyundai ix35 / Tucson 1.6 GDI 135 reaches 60 mph in 10.11 s (100 km/h in 10.70 s) and covers a standing quarter mile in 17.69 s, tripping the lights at 79.3 mph. It clears the first 60 ft in 2.96 s and the eighth mile in 11.48 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 ix35 / Tucson 1.6 GDI 135 Land Rover Freelander 1.8i 120

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 ix35 / Tucson 1.6 GDI 135
0–60 mph10.11 s
0–100 km/h10.70 s
0–100 mph—
60 ft2.96 s
1/8 mile11.48 s
1/4 mile17.69 s
Trap speed79.3 mph

About the ix35 / Tucson 1.6 GDI 135

The 2009 Hyundai ix35 / Tucson 1.6 GDI 135 is a front-drive naturally aspirated SUV of 1,492 kg with 133 bhp, which works out at 89 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.96 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,353rd quickest to 60 mph, and the 145th quickest of the 295 Hyundais here. Its 79.3 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 ix35 / Tucson 1.6 GDI 135
Year2009
Power133 hp (99 kW)
Kerb mass1,492 kg
Power to weight89 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed111 mph (179 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Freelander 1.8i 120199810.07 s17.74 s78.0 mph118 bhp
Land Rover Range Rover 3.9 V8 185198810.10 s17.70 s79.2 mph182 bhp
Proton Exora 1.6 CVT 140201210.17 s17.67 s77.8 mph138 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 SUVs2,049 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 ix35 / Tucson 1.6 GDI 135 0-60 time?
The Hyundai ix35 / Tucson 1.6 GDI 135 reaches 60 mph in 10.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,353rd quickest of the 14,946 cars in the set.
What is the Hyundai ix35 / Tucson 1.6 GDI 135 quarter mile time?
17.69 s at 79.3 mph. It reaches the eighth mile in 11.48 s and clears the first 60 ft in 2.96 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai ix35 / Tucson 1.6 GDI 135 have?
133 bhp and 1,492 kg, which is 89 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 179 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai ix35 / Tucson 1.6 GDI 135?
Closest here on pace: Land Rover Freelander 1.8i 120 (10.07 s), Land Rover Range Rover 3.9 V8 185 (10.10 s), Proton Exora 1.6 CVT 140 (10.17 s). Each one can be raced against the Hyundai ix35 / Tucson 1.6 GDI 135 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 ix35 / Tucson 1.6 GDI 135 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.