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

Chevrolet Aveo/Kalos 5dr 1.6 105

The Chevrolet Aveo/Kalos 5dr 1.6 105 reaches 60 mph in 10.12 s (100 km/h in 10.70 s) and covers a standing quarter mile in 17.67 s, tripping the lights at 79.9 mph. It clears the first 60 ft in 2.99 s and the eighth mile in 11.50 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.6 105 Mitsubishi Colt 5dr 1.3 95 (2008)

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.6 105
0–60 mph10.12 s
0–100 km/h10.70 s
0–100 mph—
60 ft2.99 s
1/8 mile11.50 s
1/4 mile17.67 s
Trap speed79.9 mph

About the Aveo/Kalos 5dr 1.6 105

The 2004 Chevrolet Aveo/Kalos 5dr 1.6 105 is a front-drive naturally aspirated car of 1,075 kg with 103 bhp, which works out at 96 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.99 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 10,361st quickest to 60 mph, and the 141st quickest of the 199 Chevrolets here. Its 79.9 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.6 105
Year2004
Power103 hp (77 kW)
Kerb mass1,075 kg
Power to weight96 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Colt 5dr 1.3 95 (2008)200810.11 s17.69 s79.4 mph94 bhp
Honda Civic 1.5 ISI199210.12 s17.69 s79.6 mph90 bhp
Mitsubishi Colt 5dr 1.3 95 (2004)200410.11 s17.69 s79.4 mph94 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 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 Chevrolet Aveo/Kalos 5dr 1.6 105 0-60 time?
The Chevrolet Aveo/Kalos 5dr 1.6 105 reaches 60 mph in 10.12 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,361st quickest of the 14,946 cars in the set.
What is the Chevrolet Aveo/Kalos 5dr 1.6 105 quarter mile time?
17.67 s at 79.9 mph. It reaches the eighth mile in 11.50 s and clears the first 60 ft in 2.99 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Aveo/Kalos 5dr 1.6 105 have?
103 bhp and 1,075 kg, which is 96 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Aveo/Kalos 5dr 1.6 105?
Closest here on pace: Mitsubishi Colt 5dr 1.3 95 (2008) (10.11 s), Honda Civic 1.5 ISI (10.12 s), Mitsubishi Colt 5dr 1.3 95 (2004) (10.11 s). Each one can be raced against the Chevrolet Aveo/Kalos 5dr 1.6 105 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.6 105 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.