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

Hyundai Coupe / Tiburon 2.0i 143

The Hyundai Coupe / Tiburon 2.0i 143 reaches 60 mph in 8.28 s (100 km/h in 8.74 s) and covers a standing quarter mile in 16.29 s, tripping the lights at 87.2 mph. It clears the first 60 ft in 2.78 s and the eighth mile in 10.65 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 Coupe / Tiburon 2.0i 143 Toyota MR2 1.6 116

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 Coupe / Tiburon 2.0i 143
0–60 mph8.28 s
0–100 km/h8.74 s
0–100 mph—
60 ft2.78 s
1/8 mile10.65 s
1/4 mile16.29 s
Trap speed87.2 mph

About the Coupe / Tiburon 2.0i 143

The 2007 Hyundai Coupe / Tiburon 2.0i 143 is a front-drive naturally aspirated coupe of 1,287 kg with 141 bhp, which works out at 109 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.78 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,080th quickest to 60 mph, and the 50th quickest of the 295 Hyundais here. Its 87.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 2 of 2 published acceleration figures for this car.

On paper

Specification Hyundai Coupe / Tiburon 2.0i 143
Year2007
Power141 hp (105 kW)
Kerb mass1,287 kg
Power to weight109 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed129 mph (208 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota MR2 1.6 11619858.19 s16.31 s85.9 mph114 bhp
Fiat Coupe 1.8 13019948.37 s16.37 s86.6 mph129 bhp
Honda Prelude 2.0i 13319928.37 s16.39 s86.3 mph131 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 coupes911 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 Coupe / Tiburon 2.0i 143 0-60 time?
The Hyundai Coupe / Tiburon 2.0i 143 reaches 60 mph in 8.28 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,080th quickest of the 14,946 cars in the set.
What is the Hyundai Coupe / Tiburon 2.0i 143 quarter mile time?
16.29 s at 87.2 mph. It reaches the eighth mile in 10.65 s and clears the first 60 ft in 2.78 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Coupe / Tiburon 2.0i 143 have?
141 bhp and 1,287 kg, which is 109 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 208 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Coupe / Tiburon 2.0i 143?
Closest here on pace: Toyota MR2 1.6 116 (8.19 s), Fiat Coupe 1.8 130 (8.37 s), Honda Prelude 2.0i 133 (8.37 s). Each one can be raced against the Hyundai Coupe / Tiburon 2.0i 143 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 Coupe / Tiburon 2.0i 143 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.