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

Kia cee'd Sportswagon 1.6 GDI 135

The Kia cee'd Sportswagon 1.6 GDI 135 reaches 60 mph in 10.01 s (100 km/h in 10.68 s) and covers a standing quarter mile in 17.53 s, tripping the lights at 79.3 mph. It clears the first 60 ft in 2.85 s and the eighth mile in 11.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.

Kia cee'd Sportswagon 1.6 GDI 135 Hyundai Sonata 2.0i 125

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 cee'd Sportswagon 1.6 GDI 135
0–60 mph10.01 s
0–100 km/h10.68 s
0–100 mph—
60 ft2.85 s
1/8 mile11.32 s
1/4 mile17.53 s
Trap speed79.3 mph

About the cee'd Sportswagon 1.6 GDI 135

The 2012 Kia cee'd Sportswagon 1.6 GDI 135 is a front-drive naturally aspirated saloon of 1,316 kg with 133 bhp, which works out at 101 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.85 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 10,175th quickest to 60 mph, and the 92nd quickest of the 205 Kias here. Its 79.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 2 of 2 published acceleration figures for this car.

On paper

Specification Kia cee'd Sportswagon 1.6 GDI 135
Year2012
Power133 hp (99 kW)
Kerb mass1,316 kg
Power to weight101 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed119 mph (192 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Sonata 2.0i 125199610.04 s17.58 s80.9 mph123 bhp
Chrysler Sebring Sedan 2.4 152200110.04 s17.57 s81.3 mph150 bhp
Suzuki Swift Sedan 1.6 92199110.02 s17.63 s79.6 mph91 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Kia 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 2010s4,541 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 cee'd Sportswagon 1.6 GDI 135 0-60 time?
The Kia cee'd Sportswagon 1.6 GDI 135 reaches 60 mph in 10.01 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,175th quickest of the 14,946 cars in the set.
What is the Kia cee'd Sportswagon 1.6 GDI 135 quarter mile time?
17.53 s at 79.3 mph. It reaches the eighth mile in 11.32 s and clears the first 60 ft in 2.85 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia cee'd Sportswagon 1.6 GDI 135 have?
133 bhp and 1,316 kg, which is 101 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 192 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia cee'd Sportswagon 1.6 GDI 135?
Closest here on pace: Hyundai Sonata 2.0i 125 (10.04 s), Chrysler Sebring Sedan 2.4 152 (10.04 s), Suzuki Swift Sedan 1.6 92 (10.02 s). Each one can be raced against the Kia cee'd Sportswagon 1.6 GDI 135 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 cee'd Sportswagon 1.6 GDI 135 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 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-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.