← My Auto Racer All cars Hyundai 0-60 Comparisons
The Hyundai Genesis 4.6 reaches 60 mph in 5.11 s and covers a standing quarter mile in 13.66 s, tripping the lights at 102.6 mph. It clears the first 60 ft in 2.19 s and the eighth mile in 8.82 s, reaching 100 mph in 12.93 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Hyundai Genesis 4.6 |
|---|---|
| 0–60 mph | 5.11 s |
| 0–100 mph | 12.93 s |
| 60 ft | 2.19 s |
| 1/8 mile | 8.82 s |
| 1/4 mile | 13.66 s |
| Trap speed | 102.6 mph |
The 2009 Hyundai Genesis 4.6 is a rear-drive naturally aspirated saloon of 1,824 kg with 375 bhp, which works out at 206 bhp per tonne. Rear drive and 206 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.19 s. Against the 2,929 cars in the set it is the 1,447th quickest to 60 mph, and the 4th quickest of the 24 Hyundais here. Its 102.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 7 of 7 published acceleration figures for this car.
| Specification | Hyundai Genesis 4.6 |
|---|---|
| Year | 2009 |
| Power | 375 bhp |
| Kerb mass | 1,824 kg |
| Power to weight | 206 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 258 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Infiniti M45 | 2006 | 5.09 s | 13.63 s | 102.3 mph | 335 bhp |
| Infiniti M35h | 2012 | 5.18 s | 13.76 s | 101.5 mph | 359 bhp |
| Genesis G90 RS4 415 PS | 2022 | 4.98 s | 13.54 s | 101.6 mph | 409 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.