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

Hyundai Veloster 1.6 GDi 140 PS

The Hyundai Veloster 1.6 GDi 140 PS reaches 60 mph in 9.15 s (100 km/h in 9.91 s) and covers a standing quarter mile in 17.19 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.90 s and the eighth mile in 11.26 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 Veloster 1.6 GDi 140 PS GMC Jimmy 5dr 4.3 V6 194

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 Veloster 1.6 GDi 140 PS
0–60 mph9.15 s
0–100 km/h9.91 s
0–100 mph—
60 ft2.90 s
1/8 mile11.26 s
1/4 mile17.19 s
Trap speed83.2 mph

About the Veloster 1.6 GDi 140 PS

The 2011 Hyundai Veloster 1.6 GDi 140 PS is a front-drive naturally aspirated car of 1,260 kg with 138 bhp, which works out at 110 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.90 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 8,699th quickest to 60 mph, and the 85th quickest of the 295 Hyundais here. Its 83.2 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 9 of 9 published acceleration figures for this car.

On paper

Specification Hyundai Veloster 1.6 GDi 140 PS
Year2011
Power138 hp (103 kW)
Kerb mass1,260 kg
Power to weight110 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
GMC Jimmy 5dr 4.3 V6 19419979.13 s17.17 s80.8 mph190 bhp
Renault 5 3dr 1.4 Alpine 9219729.18 s17.11 s81.3 mph91 bhp
Toyota Ipsum20019.16 s17.04 s85.5 mph158 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 cars0-100 km/h under 10 seconds9,062 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 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 Veloster 1.6 GDi 140 PS 0-60 time?
The Hyundai Veloster 1.6 GDi 140 PS reaches 60 mph in 9.15 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,699th quickest of the 14,946 cars in the set.
What is the Hyundai Veloster 1.6 GDi 140 PS quarter mile time?
17.19 s at 83.2 mph. It reaches the eighth mile in 11.26 s and clears the first 60 ft in 2.90 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Veloster 1.6 GDi 140 PS have?
138 bhp and 1,260 kg, which is 110 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Veloster 1.6 GDi 140 PS?
Closest here on pace: GMC Jimmy 5dr 4.3 V6 194 (9.13 s), Renault 5 3dr 1.4 Alpine 92 (9.18 s), Toyota Ipsum (9.16 s). Each one can be raced against the Hyundai Veloster 1.6 GDi 140 PS 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 Veloster 1.6 GDi 140 PS is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 9 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.