← My Auto Racer All cars Hyundai 0-60 Comparisons
The Hyundai i20 N BC3 reaches 60 mph in 5.66 s and covers a standing quarter mile in 14.30 s, tripping the lights at 96.8 mph. It clears the first 60 ft in 2.24 s and the eighth mile in 9.22 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 i20 N BC3 |
|---|---|
| 0–60 mph | 5.66 s |
| 0–100 mph | — |
| 60 ft | 2.24 s |
| 1/8 mile | 9.22 s |
| 1/4 mile | 14.30 s |
| Trap speed | 96.8 mph |
The 2021 Hyundai i20 N BC3 is a front-drive turbocharged car of 1,190 kg with 201 bhp, which works out at 169 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.24 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 1,767th quickest to 60 mph, and the 6th quickest of the 24 Hyundais here. It leaves better than it pulls: 96.8 mph at the lights is only the 1,994th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Hyundai i20 N BC3 |
|---|---|
| Year | 2021 |
| Power | 201 bhp |
| Kerb mass | 1,190 kg |
| Power to weight | 169 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 230 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Citroen DS3 Performance | 2016 | 5.69 s | 14.29 s | 97.6 mph | 205 bhp |
| Acura TSX V-6 | 2010 | 5.71 s | 14.34 s | 97.8 mph | 280 bhp |
| Honda Accord 2.0T Mk X | 2018 | 5.72 s | 14.32 s | 99.5 mph | 252 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.