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

Kia Optima / Magentis 1.7 CRDi 136

The Kia Optima / Magentis 1.7 CRDi 136 reaches 60 mph in 10.47 s (100 km/h in 11.16 s) and covers a standing quarter mile in 17.66 s, tripping the lights at 77.9 mph. It clears the first 60 ft in 2.71 s and the eighth mile in 11.31 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 Optima / Magentis 1.7 CRDi 136 Lancia Kappa 2.4 Turbo 124

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 Optima / Magentis 1.7 CRDi 136
0–60 mph10.47 s
0–100 km/h11.16 s
0–100 mph—
60 ft2.71 s
1/8 mile11.31 s
1/4 mile17.66 s
Trap speed77.9 mph

About the Optima / Magentis 1.7 CRDi 136

The 2010 Kia Optima / Magentis 1.7 CRDi 136 is a front-drive turbodiesel saloon of 1,595 kg with 134 bhp, which works out at 84 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.71 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,940th quickest to 60 mph, and the 122nd quickest of the 205 Kias here. Its 77.9 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 Optima / Magentis 1.7 CRDi 136
Year2010
Power134 hp (100 kW)
Kerb mass1,595 kg
Power to weight84 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed122 mph (196 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Kappa 2.4 Turbo 124199510.44 s17.71 s77.9 mph122 bhp
SEAT Altea XL 1.2 TSI 105200910.53 s17.69 s77.1 mph103 bhp
Mazda 626 (Mk.5) Sedan 2.0 DiTD 100199710.42 s17.74 s77.5 mph99 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 Optima / Magentis 1.7 CRDi 136 0-60 time?
The Kia Optima / Magentis 1.7 CRDi 136 reaches 60 mph in 10.47 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,940th quickest of the 14,946 cars in the set.
What is the Kia Optima / Magentis 1.7 CRDi 136 quarter mile time?
17.66 s at 77.9 mph. It reaches the eighth mile in 11.31 s and clears the first 60 ft in 2.71 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Optima / Magentis 1.7 CRDi 136 have?
134 bhp and 1,595 kg, which is 84 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 196 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Optima / Magentis 1.7 CRDi 136?
Closest here on pace: Lancia Kappa 2.4 Turbo 124 (10.44 s), SEAT Altea XL 1.2 TSI 105 (10.53 s), Mazda 626 (Mk.5) Sedan 2.0 DiTD 100 (10.42 s). Each one can be raced against the Kia Optima / Magentis 1.7 CRDi 136 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 Optima / Magentis 1.7 CRDi 136 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.