← My Auto Racer All cars Kia 0-60 Comparisons Answers

Kia Pro Ceed 2.0 CVVT Mk I

The Kia Pro Ceed 2.0 CVVT Mk I reaches 60 mph in 8.39 s (100 km/h in 8.90 s) and covers a standing quarter mile in 16.58 s, tripping the lights at 84.3 mph. It clears the first 60 ft in 2.70 s and the eighth mile in 10.74 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.

Kia Pro Ceed 2.0 CVVT Mk I Fiat Stilo 5dr 1.9 JTD 140

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Kia Pro Ceed 2.0 CVVT Mk I
0–60 mph8.39 s
0–100 km/h8.90 s
0–100 mph—
60 ft2.70 s
1/8 mile10.74 s
1/4 mile16.58 s
Trap speed84.3 mph

About the Pro Ceed 2.0 CVVT Mk I

The 2008 Kia Pro Ceed 2.0 CVVT Mk I is a front-drive naturally aspirated car of 1,342 kg with 141 bhp, which works out at 105 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.70 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 7,277th quickest to 60 mph, and the 34th quickest of the 205 Kias here. Its 84.3 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 9 published acceleration figures for this car.

On paper

Specification Kia Pro Ceed 2.0 CVVT Mk I
Year2008
Power141 hp (105 kW)
Kerb mass1,342 kg
Power to weight105 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed127 mph (205 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Fiat Stilo 5dr 1.9 JTD 14020018.41 s16.57 s83.0 mph138 bhp
MINI Clubvan Cooper 1.6 12220128.43 s16.64 s83.8 mph121 bhp
Hyundai Veloster 1.6 Blue 14020118.35 s16.58 s84.1 mph138 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.

Where these times sit

0-60 under 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Kia 0-60 timesevery modelFastest hatchbacks4,513 carsFastest cars of the 2000s5,138 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Kia Pro Ceed 2.0 CVVT Mk I 0-60 time?
The Kia Pro Ceed 2.0 CVVT Mk I reaches 60 mph in 8.39 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,277th quickest of the 14,946 cars in the set.
What is the Kia Pro Ceed 2.0 CVVT Mk I quarter mile time?
16.58 s at 84.3 mph. It reaches the eighth mile in 10.74 s and clears the first 60 ft in 2.70 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Pro Ceed 2.0 CVVT Mk I have?
141 bhp and 1,342 kg, which is 105 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 205 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Pro Ceed 2.0 CVVT Mk I?
Closest here on pace: Fiat Stilo 5dr 1.9 JTD 140 (8.41 s), MINI Clubvan Cooper 1.6 122 (8.43 s), Hyundai Veloster 1.6 Blue 140 (8.35 s). Each one can be raced against the Kia Pro Ceed 2.0 CVVT Mk I in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Kia Pro Ceed 2.0 CVVT Mk I is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 9 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.