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

Kia Optima / Magentis 2.0 D 147

The Kia Optima / Magentis 2.0 D 147 reaches 60 mph in 8.94 s (100 km/h in 10.01 s) and covers a standing quarter mile in 16.90 s, tripping the lights at 81.2 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.87 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 2.0 D 147 Alfa Romeo 166 2.4 JTD 136

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 2.0 D 147
0–60 mph8.94 s
0–100 km/h10.01 s
0–100 mph—
60 ft2.55 s
1/8 mile10.87 s
1/4 mile16.90 s
Trap speed81.2 mph

About the Optima / Magentis 2.0 D 147

The 2008 Kia Optima / Magentis 2.0 D 147 is a front-drive turbodiesel saloon of 1,603 kg with 148 bhp, which works out at 92 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 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 8,333rd quickest to 60 mph, and the 46th quickest of the 205 Kias here. It leaves better than it pulls: 81.2 mph at the lights is only the 9,335th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Kia Optima / Magentis 2.0 D 147
Year2008
Power148 hp (110 kW)
Kerb mass1,603 kg
Power to weight92 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Alfa Romeo 166 2.4 JTD 13619968.93 s16.88 s82.6 mph134 bhp
Peugeot 508 1.5 BlueHDI 13020198.94 s16.87 s82.8 mph129 bhp
Skoda Superb 2.0 TDI 140 (2002)20028.95 s16.86 s83.0 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 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 saloon cars3,808 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 Optima / Magentis 2.0 D 147 0-60 time?
The Kia Optima / Magentis 2.0 D 147 reaches 60 mph in 8.94 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,333rd quickest of the 14,946 cars in the set.
What is the Kia Optima / Magentis 2.0 D 147 quarter mile time?
16.90 s at 81.2 mph. It reaches the eighth mile in 10.87 s and clears the first 60 ft in 2.55 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Optima / Magentis 2.0 D 147 have?
148 bhp and 1,603 kg, which is 92 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Kia Optima / Magentis 2.0 D 147?
Closest here on pace: Alfa Romeo 166 2.4 JTD 136 (8.93 s), Peugeot 508 1.5 BlueHDI 130 (8.94 s), Skoda Superb 2.0 TDI 140 (2002) (8.95 s). Each one can be raced against the Kia Optima / Magentis 2.0 D 147 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 2.0 D 147 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.