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

Chevrolet Aveo/Kalos Sedan 1.4 94

The Chevrolet Aveo/Kalos Sedan 1.4 94 reaches 60 mph in 10.10 s (100 km/h in 10.70 s) and covers a standing quarter mile in 17.70 s, tripping the lights at 79.1 mph. It clears the first 60 ft in 2.94 s and the eighth mile in 11.46 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 Sedan 1.4 94 Mitsubishi Lancer 1.6 MIVEC 117

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 Sedan 1.4 94
0–60 mph10.10 s
0–100 km/h10.70 s
0–100 mph—
60 ft2.94 s
1/8 mile11.46 s
1/4 mile17.70 s
Trap speed79.1 mph

About the Aveo/Kalos Sedan 1.4 94

The 2005 Chevrolet Aveo/Kalos Sedan 1.4 94 is a front-drive naturally aspirated saloon of 1,052 kg with 93 bhp, which works out at 88 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.94 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,336th quickest to 60 mph, and the 139th quickest of the 199 Chevrolets here. Its 79.1 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 Sedan 1.4 94
Year2005
Power93 hp (69 kW)
Kerb mass1,052 kg
Power to weight88 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed109 mph (176 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Lancer 1.6 MIVEC 117200710.13 s17.65 s80.4 mph115 bhp
Volvo S60 2.4 140200810.00 s17.68 s81.9 mph138 bhp
Daewoo Espero 1.8 95199010.02 s17.63 s79.6 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 saloon cars3,808 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 Sedan 1.4 94 0-60 time?
The Chevrolet Aveo/Kalos Sedan 1.4 94 reaches 60 mph in 10.10 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,336th quickest of the 14,946 cars in the set.
What is the Chevrolet Aveo/Kalos Sedan 1.4 94 quarter mile time?
17.70 s at 79.1 mph. It reaches the eighth mile in 11.46 s and clears the first 60 ft in 2.94 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Aveo/Kalos Sedan 1.4 94 have?
93 bhp and 1,052 kg, which is 88 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 176 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Aveo/Kalos Sedan 1.4 94?
Closest here on pace: Mitsubishi Lancer 1.6 MIVEC 117 (10.13 s), Volvo S60 2.4 140 (10.00 s), Daewoo Espero 1.8 95 (10.02 s). Each one can be raced against the Chevrolet Aveo/Kalos Sedan 1.4 94 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 Sedan 1.4 94 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.