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

Daewoo Lacetti Wagon 1.8 122

The Daewoo Lacetti Wagon 1.8 122 reaches 60 mph in 10.91 s (100 km/h in 11.50 s) and covers a standing quarter mile in 18.48 s, tripping the lights at 80.1 mph. It clears the first 60 ft in 3.29 s and the eighth mile in 12.30 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 Lacetti Wagon 1.8 122 Suzuki Wagon R 1.3 16V 94

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 Lacetti Wagon 1.8 122
0–60 mph10.91 s
0–100 km/h11.50 s
0–100 mph—
60 ft3.29 s
1/8 mile12.30 s
1/4 mile18.48 s
Trap speed80.1 mph

About the Lacetti Wagon 1.8 122

The 2003 Daewoo Lacetti Wagon 1.8 122 is a front-drive naturally aspirated estate of 1,305 kg with 121 bhp, which works out at 92 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.29 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 11,531st quickest to 60 mph, and the 26th quickest of the 45 Daewoos here. It traps higher than its 0-60 suggests — 80.1 mph, the 10,001st 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 Lacetti Wagon 1.8 122
Year2003
Power121 hp (90 kW)
Kerb mass1,305 kg
Power to weight92 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed114 mph (183 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Suzuki Wagon R 1.3 16V 94200311.01 s18.35 s75.0 mph93 bhp
Chevrolet Nubira/Lacetti 4dr 1.8 122200410.91 s18.48 s80.1 mph121 bhp
Skoda Octavia I Combi 1.6 102199710.86 s18.13 s78.6 mph101 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
Daewoo 0-60 timesevery modelFastest estate cars1,484 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 Lacetti Wagon 1.8 122 0-60 time?
The Daewoo Lacetti Wagon 1.8 122 reaches 60 mph in 10.91 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,531st quickest of the 14,946 cars in the set.
What is the Daewoo Lacetti Wagon 1.8 122 quarter mile time?
18.48 s at 80.1 mph. It reaches the eighth mile in 12.30 s and clears the first 60 ft in 3.29 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Daewoo Lacetti Wagon 1.8 122 have?
121 bhp and 1,305 kg, which is 92 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 183 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Daewoo Lacetti Wagon 1.8 122?
Closest here on pace: Suzuki Wagon R 1.3 16V 94 (11.01 s), Chevrolet Nubira/Lacetti 4dr 1.8 122 (10.91 s), Skoda Octavia I Combi 1.6 102 (10.86 s). Each one can be raced against the Daewoo Lacetti Wagon 1.8 122 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 Lacetti Wagon 1.8 122 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.