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

Hyundai Sonata 2.0i 5MTFWD 139

The Hyundai Sonata 2.0i 5MTFWD 139 reaches 60 mph in 9.30 s (100 km/h in 9.82 s) and covers a standing quarter mile in 17.07 s, tripping the lights at 82.8 mph. It clears the first 60 ft in 2.90 s and the eighth mile in 11.13 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 Sonata 2.0i 5MTFWD 139 Acura Legend 2.5 V6 151

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 Sonata 2.0i 5MTFWD 139
0–60 mph9.30 s
0–100 km/h9.82 s
0–100 mph—
60 ft2.90 s
1/8 mile11.13 s
1/4 mile17.07 s
Trap speed82.8 mph

About the Sonata 2.0i 5MTFWD 139

The 1994 Hyundai Sonata 2.0i 5MTFWD 139 is a front-drive naturally aspirated saloon of 1,194 kg with 137 bhp, which works out at 115 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,949th quickest to 60 mph, and the 95th quickest of the 295 Hyundais here. Its 82.8 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 Sonata 2.0i 5MTFWD 139
Year1994
Power137 hp (102 kW)
Kerb mass1,194 kg
Power to weight115 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Acura Legend 2.5 V6 15119869.30 s17.04 s83.9 mph150 bhp
Holden Cruze 1.4 Turbo 14020089.32 s17.11 s80.7 mph138 bhp
Jaguar XJ 4.2 20819799.39 s17.13 s82.8 mph205 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 saloon cars3,808 carsFastest cars of the 1990s2,649 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 Sonata 2.0i 5MTFWD 139 0-60 time?
The Hyundai Sonata 2.0i 5MTFWD 139 reaches 60 mph in 9.30 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,949th quickest of the 14,946 cars in the set.
What is the Hyundai Sonata 2.0i 5MTFWD 139 quarter mile time?
17.07 s at 82.8 mph. It reaches the eighth mile in 11.13 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 Sonata 2.0i 5MTFWD 139 have?
137 bhp and 1,194 kg, which is 115 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Sonata 2.0i 5MTFWD 139?
Closest here on pace: Acura Legend 2.5 V6 151 (9.30 s), Holden Cruze 1.4 Turbo 140 (9.32 s), Jaguar XJ 4.2 208 (9.39 s). Each one can be raced against the Hyundai Sonata 2.0i 5MTFWD 139 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 Sonata 2.0i 5MTFWD 139 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.