← My Auto Racer All cars Kia 0-60 Comparisons
The Kia Stinger 2.0T 256 PS reaches 60 mph in 6.13 s and covers a standing quarter mile in 14.66 s, tripping the lights at 96.0 mph. It clears the first 60 ft in 2.35 s and the eighth mile in 9.50 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 | Kia Stinger 2.0T 256 PS |
|---|---|
| 0–60 mph | 6.13 s |
| 0–100 mph | — |
| 60 ft | 2.35 s |
| 1/8 mile | 9.50 s |
| 1/4 mile | 14.66 s |
| Trap speed | 96.0 mph |
The 2017 Kia Stinger 2.0T 256 PS is a rear-drive turbocharged car of 1,638 kg with 255 bhp, which works out at 156 bhp per tonne. Rear drive and 156 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.35 s. Against the 2,929 cars in the set it is the 2,009th quickest to 60 mph, and the 5th quickest of the 16 Kias here. Its 96.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 9 of 10 published acceleration figures for this car.
| Specification | Kia Stinger 2.0T 256 PS |
|---|---|
| Year | 2017 |
| Power | 255 bhp |
| Kerb mass | 1,638 kg |
| Power to weight | 156 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 240 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ford Fiesta ST (Mk8) | 2019 | 6.14 s | 14.58 s | 96.2 mph | 197 bhp |
| Land Rover Discovery P360 Mk V | 2020 | 6.09 s | 14.68 s | 95.8 mph | 355 bhp |
| MINI Cooper S 184 PS | 2010 | 6.11 s | 14.72 s | 93.5 mph | 181 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.