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

Daewoo Lacetti 5dr 1.5 106

The Daewoo Lacetti 5dr 1.5 106 reaches 60 mph in 11.19 s (100 km/h in 11.79 s) and covers a standing quarter mile in 18.66 s, tripping the lights at 79.5 mph. It clears the first 60 ft in 3.33 s and the eighth mile in 12.44 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 5dr 1.5 106 Chevrolet Aveo/Kalos 5dr 1.4 DOHC 101

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 5dr 1.5 106
0–60 mph11.19 s
0–100 km/h11.79 s
0–100 mph—
60 ft3.33 s
1/8 mile12.44 s
1/4 mile18.66 s
Trap speed79.5 mph

About the Lacetti 5dr 1.5 106

The 2003 Daewoo Lacetti 5dr 1.5 106 is a front-drive naturally aspirated car of 1,150 kg with 105 bhp, which works out at 91 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.33 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,897th quickest to 60 mph, and the 32nd quickest of the 45 Daewoos here. It traps higher than its 0-60 suggests — 79.5 mph, the 10,297th 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 5dr 1.5 106
Year2003
Power105 hp (78 kW)
Kerb mass1,150 kg
Power to weight91 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed114 mph (183 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Aveo/Kalos 5dr 1.4 DOHC 101200811.24 s18.72 s78.0 mph99 bhp
Honda Accord Hatchback 1.8 136200111.14 s18.59 s81.5 mph134 bhp
Chevrolet Aveo/Kalos 5dr 1.4 16V 100200511.23 s18.72 s78.0 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
Daewoo 0-60 timesevery modelFastest hatchbacks4,513 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 5dr 1.5 106 0-60 time?
The Daewoo Lacetti 5dr 1.5 106 reaches 60 mph in 11.19 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,897th quickest of the 14,946 cars in the set.
What is the Daewoo Lacetti 5dr 1.5 106 quarter mile time?
18.66 s at 79.5 mph. It reaches the eighth mile in 12.44 s and clears the first 60 ft in 3.33 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Daewoo Lacetti 5dr 1.5 106 have?
105 bhp and 1,150 kg, which is 91 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 5dr 1.5 106?
Closest here on pace: Chevrolet Aveo/Kalos 5dr 1.4 DOHC 101 (11.24 s), Honda Accord Hatchback 1.8 136 (11.14 s), Chevrolet Aveo/Kalos 5dr 1.4 16V 100 (11.23 s). Each one can be raced against the Daewoo Lacetti 5dr 1.5 106 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 5dr 1.5 106 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.