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

Daewoo Magnus 2.0 130

The Daewoo Magnus 2.0 130 reaches 60 mph in 9.45 s (100 km/h in 9.93 s) and covers a standing quarter mile in 17.41 s, tripping the lights at 85.0 mph. It clears the first 60 ft in 3.08 s and the eighth mile in 11.59 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.

Daewoo Magnus 2.0 130 Lincoln Continental 3.8 V6 155

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 Daewoo Magnus 2.0 130
0–60 mph9.45 s
0–100 km/h9.93 s
0–100 mph—
60 ft3.08 s
1/8 mile11.59 s
1/4 mile17.41 s
Trap speed85.0 mph

About the Magnus 2.0 130

The 2002 Daewoo Magnus 2.0 130 is a front-drive naturally aspirated saloon of 1,330 kg with 129 bhp, which works out at 97 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.08 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 9,176th quickest to 60 mph, and the 10th quickest of the 45 Daewoos here. It traps higher than its 0-60 suggests — 85.0 mph, the 7,285th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Daewoo Magnus 2.0 130
Year2002
Power129 hp (96 kW)
Kerb mass1,330 kg
Power to weight97 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lincoln Continental 3.8 V6 15519889.44 s17.42 s84.7 mph156 bhp
Mazda 6/Atenza Sedan 2.0 14520129.50 s17.33 s81.7 mph143 bhp
Nissan Tiida/Versa Sedan 1.6 16V 11220069.47 s17.24 s81.5 mph110 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
Daewoo 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 Daewoo Magnus 2.0 130 0-60 time?
The Daewoo Magnus 2.0 130 reaches 60 mph in 9.45 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,176th quickest of the 14,946 cars in the set.
What is the Daewoo Magnus 2.0 130 quarter mile time?
17.41 s at 85.0 mph. It reaches the eighth mile in 11.59 s and clears the first 60 ft in 3.08 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Daewoo Magnus 2.0 130 have?
129 bhp and 1,330 kg, which is 97 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Daewoo Magnus 2.0 130?
Closest here on pace: Lincoln Continental 3.8 V6 155 (9.44 s), Mazda 6/Atenza Sedan 2.0 145 (9.50 s), Nissan Tiida/Versa Sedan 1.6 16V 112 (9.47 s). Each one can be raced against the Daewoo Magnus 2.0 130 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 Daewoo Magnus 2.0 130 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.