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

Hyundai Elantra 4dr 2.0i 141

The Hyundai Elantra 4dr 2.0i 141 reaches 60 mph in 8.28 s (100 km/h in 8.74 s) and covers a standing quarter mile in 16.30 s, tripping the lights at 87.0 mph. It clears the first 60 ft in 2.77 s and the eighth mile in 10.64 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 Elantra 4dr 2.0i 141 Toyota Yaris TS 5dr 1.8 Dual VVT-i

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 Elantra 4dr 2.0i 141
0–60 mph8.28 s
0–100 km/h8.74 s
0–100 mph—
60 ft2.77 s
1/8 mile10.64 s
1/4 mile16.30 s
Trap speed87.0 mph

About the Elantra 4dr 2.0i 141

The 2000 Hyundai Elantra 4dr 2.0i 141 is a front-drive naturally aspirated car of 1,193 kg with 139 bhp, which works out at 117 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.77 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 7,085th quickest to 60 mph, and the 53rd quickest of the 295 Hyundais here. Its 87.0 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 Elantra 4dr 2.0i 141
Year2000
Power139 hp (104 kW)
Kerb mass1,193 kg
Power to weight117 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed128 mph (206 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota Yaris TS 5dr 1.8 Dual VVT-i20078.28 s16.25 s86.0 mph131 bhp
SEAT Cordoba SX 1.8 12919968.28 s16.30 s87.0 mph127 bhp
Alfa Romeo 145 1.8 TS 14419948.28 s16.29 s87.2 mph142 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 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 Elantra 4dr 2.0i 141 0-60 time?
The Hyundai Elantra 4dr 2.0i 141 reaches 60 mph in 8.28 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,085th quickest of the 14,946 cars in the set.
What is the Hyundai Elantra 4dr 2.0i 141 quarter mile time?
16.30 s at 87.0 mph. It reaches the eighth mile in 10.64 s and clears the first 60 ft in 2.77 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Elantra 4dr 2.0i 141 have?
139 bhp and 1,193 kg, which is 117 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 206 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Elantra 4dr 2.0i 141?
Closest here on pace: Toyota Yaris TS 5dr 1.8 Dual VVT-i (8.28 s), SEAT Cordoba SX 1.8 129 (8.28 s), Alfa Romeo 145 1.8 TS 144 (8.28 s). Each one can be raced against the Hyundai Elantra 4dr 2.0i 141 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 Elantra 4dr 2.0i 141 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.