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

Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84

The Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 reaches 60 mph in 11.65 s (100 km/h in 12.37 s) and covers a standing quarter mile in 18.68 s, tripping the lights at 75.2 mph. It clears the first 60 ft in 3.15 s and the eighth mile in 12.13 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.

Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 Daihatsu Valera 1.5 75

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 Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84
0–60 mph11.65 s
0–100 km/h12.37 s
0–100 mph—
60 ft3.15 s
1/8 mile12.13 s
1/4 mile18.68 s
Trap speed75.2 mph

About the Aveo/Kalos 5dr 1.2 DOHC 84

The 2008 Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 is a front-drive naturally aspirated car of 1,005 kg with 83 bhp, which works out at 83 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.15 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 12,418th quickest to 60 mph, and the 178th quickest of the 199 Chevrolets here. Its 75.2 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 Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84
Year2008
Power83 hp (62 kW)
Kerb mass1,005 kg
Power to weight83 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed106 mph (170 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Daihatsu Valera 1.5 75199611.60 s18.69 s74.3 mph74 bhp
SEAT Altea 1.6 102200411.68 s18.67 s76.0 mph101 bhp
SEAT Altea 1.6 8v 102200911.68 s18.67 s76.0 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
Chevrolet 0-60 timesevery modelFastest small cars1,681 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 Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 0-60 time?
The Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 reaches 60 mph in 11.65 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,418th quickest of the 14,946 cars in the set.
What is the Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 quarter mile time?
18.68 s at 75.2 mph. It reaches the eighth mile in 12.13 s and clears the first 60 ft in 3.15 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 have?
83 bhp and 1,005 kg, which is 83 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 170 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84?
Closest here on pace: Daihatsu Valera 1.5 75 (11.60 s), SEAT Altea 1.6 102 (11.68 s), SEAT Altea 1.6 8v 102 (11.68 s). Each one can be raced against the Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 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 Chevrolet Aveo/Kalos 5dr 1.2 DOHC 84 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.