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

Honda Airwave 1.5 CVT 110

The Honda Airwave 1.5 CVT 110 reaches 60 mph in 10.51 s (100 km/h in 11.29 s) and covers a standing quarter mile in 17.88 s, tripping the lights at 76.0 mph. It clears the first 60 ft in 2.79 s and the eighth mile in 11.43 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.

Honda Airwave 1.5 CVT 110 Proton Satria Neo 1.6 5TM 110

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 Honda Airwave 1.5 CVT 110
0–60 mph10.51 s
0–100 km/h11.29 s
0–100 mph—
60 ft2.79 s
1/8 mile11.43 s
1/4 mile17.88 s
Trap speed76.0 mph

About the Airwave 1.5 CVT 110

The 2005 Honda Airwave 1.5 CVT 110 is a front-drive naturally aspirated car of 1,160 kg with 109 bhp, which works out at 94 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.79 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,003rd quickest to 60 mph, and the 132nd quickest of the 191 Hondas here. It leaves better than it pulls: 76.0 mph at the lights is only the 12,173rd highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Honda Airwave 1.5 CVT 110
Year2005
Power109 hp (81 kW)
Kerb mass1,160 kg
Power to weight94 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed104 mph (167 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Proton Satria Neo 1.6 5TM 110200610.49 s17.89 s79.4 mph110 bhp
Daewoo Lanos 1.6 106199610.48 s17.92 s78.6 mph105 bhp
Daewoo Lanos Hatchback 3dr 1.6 107199610.48 s17.92 s78.6 mph105 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.

Head to head

Kia Niro 1.6 GDI 104 vs Honda Airwave 1.5 CVT 110Full comparison

Where these times sit

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Honda 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 Honda Airwave 1.5 CVT 110 0-60 time?
The Honda Airwave 1.5 CVT 110 reaches 60 mph in 10.51 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,003rd quickest of the 14,946 cars in the set.
What is the Honda Airwave 1.5 CVT 110 quarter mile time?
17.88 s at 76.0 mph. It reaches the eighth mile in 11.43 s and clears the first 60 ft in 2.79 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Airwave 1.5 CVT 110 have?
109 bhp and 1,160 kg, which is 94 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 167 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Airwave 1.5 CVT 110?
Closest here on pace: Proton Satria Neo 1.6 5TM 110 (10.49 s), Daewoo Lanos 1.6 106 (10.48 s), Daewoo Lanos Hatchback 3dr 1.6 107 (10.48 s). Each one can be raced against the Honda Airwave 1.5 CVT 110 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 Honda Airwave 1.5 CVT 110 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.