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

Hyundai Sonata 2.0 CRDi 140

The Hyundai Sonata 2.0 CRDi 140 reaches 60 mph in 9.20 s (100 km/h in 10.30 s) and covers a standing quarter mile in 17.06 s, tripping the lights at 81.6 mph. It clears the first 60 ft in 2.58 s and the eighth mile in 10.96 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.0 CRDi 140 Volvo V90 2.0 D3 150 (2019)

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.0 CRDi 140
0–60 mph9.20 s
0–100 km/h10.30 s
0–100 mph—
60 ft2.58 s
1/8 mile10.96 s
1/4 mile17.06 s
Trap speed81.6 mph

About the Sonata 2.0 CRDi 140

The 2006 Hyundai Sonata 2.0 CRDi 140 is a front-drive turbodiesel saloon of 1,581 kg with 138 bhp, which works out at 87 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.58 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,776th quickest to 60 mph, and the 88th quickest of the 295 Hyundais here. Its 81.6 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.0 CRDi 140
Year2006
Power138 hp (103 kW)
Kerb mass1,581 kg
Power to weight87 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed126 mph (203 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo V90 2.0 D3 150 (2019)20199.19 s17.05 s81.7 mph148 bhp
Dodge Avenger 2.0 CRD 14020079.18 s16.95 s80.6 mph138 bhp
Mazda 3 / Axela Sedan 2.0 SKYACTIV-G 120 (2013)20139.08 s17.07 s81.6 mph118 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 saloon cars3,808 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 Sonata 2.0 CRDi 140 0-60 time?
The Hyundai Sonata 2.0 CRDi 140 reaches 60 mph in 9.20 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,776th quickest of the 14,946 cars in the set.
What is the Hyundai Sonata 2.0 CRDi 140 quarter mile time?
17.06 s at 81.6 mph. It reaches the eighth mile in 10.96 s and clears the first 60 ft in 2.58 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Sonata 2.0 CRDi 140 have?
138 bhp and 1,581 kg, which is 87 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 203 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Sonata 2.0 CRDi 140?
Closest here on pace: Volvo V90 2.0 D3 150 (2019) (9.19 s), Dodge Avenger 2.0 CRD 140 (9.18 s), Mazda 3 / Axela Sedan 2.0 SKYACTIV-G 120 (2013) (9.08 s). Each one can be raced against the Hyundai Sonata 2.0 CRDi 140 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.0 CRDi 140 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.