← My Auto Racer All cars Kia 0-60 Comparisons
The Kia Pro Ceed GT Mk II reaches 60 mph in 6.40 s and covers a standing quarter mile in 14.95 s, tripping the lights at 93.4 mph. It clears the first 60 ft in 2.38 s and the eighth mile in 9.67 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 Pro Ceed GT Mk II |
|---|---|
| 0–60 mph | 6.40 s |
| 0–100 mph | — |
| 60 ft | 2.38 s |
| 1/8 mile | 9.67 s |
| 1/4 mile | 14.95 s |
| Trap speed | 93.4 mph |
The 2013 Kia Pro Ceed GT Mk II is a front-drive turbocharged coupe of 1,284 kg with 201 bhp, which works out at 157 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.38 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 2,150th quickest to 60 mph, and the 7th quickest of the 16 Kias here. Its 93.4 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 Pro Ceed GT Mk II |
|---|---|
| Year | 2013 |
| Power | 201 bhp |
| Kerb mass | 1,284 kg |
| Power to weight | 157 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 230 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Subaru BRZ | 2012 | 6.39 s | 14.94 s | 93.4 mph | 197 bhp |
| Toyota GT86 | 2012 | 6.39 s | 14.89 s | 95.5 mph | 197 bhp |
| Rover 220 Coupe Turbo | 1992 | 6.42 s | 14.83 s | 98.3 mph | 197 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.