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

Daewoo Tacuma/Rezzo 1.8 101 (2000)

The Daewoo Tacuma/Rezzo 1.8 101 (2000) reaches 60 mph in 10.94 s (100 km/h in 11.58 s) and covers a standing quarter mile in 18.21 s, tripping the lights at 77.6 mph. It clears the first 60 ft in 3.10 s and the eighth mile in 11.86 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 Tacuma/Rezzo 1.8 101 (2000) Nissan Juke 1.6i 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 Tacuma/Rezzo 1.8 101 (2000)
0–60 mph10.94 s
0–100 km/h11.58 s
0–100 mph—
60 ft3.10 s
1/8 mile11.86 s
1/4 mile18.21 s
Trap speed77.6 mph

About the Tacuma/Rezzo 1.8 101

The 2000 Daewoo Tacuma/Rezzo 1.8 101 (2000) is a front-drive naturally aspirated SUV of 1,244 kg with 99 bhp, which works out at 80 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.10 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,582nd quickest to 60 mph, and the 28th quickest of the 45 Daewoos here. Its 77.6 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 Daewoo Tacuma/Rezzo 1.8 101 (2000)
Year2000
Power99 hp (74 kW)
Kerb mass1,244 kg
Power to weight80 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Nissan Juke 1.6i 94201010.90 s18.25 s76.4 mph93 bhp
Chevrolet Captiva 2.0 150200611.00 s18.17 s76.0 mph148 bhp
Land Rover Range Rover 3.5 V8 167198810.92 s18.24 s76.7 mph165 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 SUVs2,049 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 Tacuma/Rezzo 1.8 101 (2000) 0-60 time?
The Daewoo Tacuma/Rezzo 1.8 101 (2000) reaches 60 mph in 10.94 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,582nd quickest of the 14,946 cars in the set.
What is the Daewoo Tacuma/Rezzo 1.8 101 (2000) quarter mile time?
18.21 s at 77.6 mph. It reaches the eighth mile in 11.86 s and clears the first 60 ft in 3.10 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Daewoo Tacuma/Rezzo 1.8 101 (2000) have?
99 bhp and 1,244 kg, which is 80 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Daewoo Tacuma/Rezzo 1.8 101 (2000)?
Closest here on pace: Nissan Juke 1.6i 94 (10.90 s), Chevrolet Captiva 2.0 150 (11.00 s), Land Rover Range Rover 3.5 V8 167 (10.92 s). Each one can be raced against the Daewoo Tacuma/Rezzo 1.8 101 (2000) 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 Tacuma/Rezzo 1.8 101 (2000) 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.