← My Auto Racer All cars Honda 0-60 Comparisons
The Honda Accord 2.0T Mk X reaches 60 mph in 5.72 s and covers a standing quarter mile in 14.32 s, tripping the lights at 99.5 mph. It clears the first 60 ft in 2.31 s and the eighth mile in 9.32 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 | Honda Accord 2.0T Mk X |
|---|---|
| 0–60 mph | 5.72 s |
| 0–100 mph | — |
| 60 ft | 2.31 s |
| 1/8 mile | 9.32 s |
| 1/4 mile | 14.32 s |
| Trap speed | 99.5 mph |
The 2018 Honda Accord 2.0T Mk X is a front-drive turbocharged car of 1,525 kg with 252 bhp, which works out at 165 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.31 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,812th quickest to 60 mph, and the 13th quickest of the 41 Hondas here. Its 99.5 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 | Honda Accord 2.0T Mk X |
|---|---|
| Year | 2018 |
| Power | 252 bhp |
| Kerb mass | 1,525 kg |
| Power to weight | 165 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 203 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Acura TSX V-6 | 2010 | 5.71 s | 14.34 s | 97.8 mph | 280 bhp |
| Citroen DS3 Performance | 2016 | 5.69 s | 14.29 s | 97.6 mph | 205 bhp |
| Hyundai i20 N BC3 | 2021 | 5.66 s | 14.30 s | 96.8 mph | 201 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.