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

Honda Civic Coupe 1.6i 105

The Honda Civic Coupe 1.6i 105 reaches 60 mph in 9.25 s (100 km/h in 9.73 s) and covers a standing quarter mile in 17.29 s, tripping the lights at 84.9 mph. It clears the first 60 ft in 3.06 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.

Honda Civic Coupe 1.6i 105 Lancia 2000 Coupe 2.0 125

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 Civic Coupe 1.6i 105
0–60 mph9.25 s
0–100 km/h9.73 s
0–100 mph—
60 ft3.06 s
1/8 mile11.46 s
1/4 mile17.29 s
Trap speed84.9 mph

About the Civic Coupe 1.6i 105

The 1996 Honda Civic Coupe 1.6i 105 is a front-drive naturally aspirated coupe of 1,000 kg with 103 bhp, which works out at 103 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.06 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 8,861st quickest to 60 mph, and the 90th quickest of the 191 Hondas here. It traps higher than its 0-60 suggests — 84.9 mph, the 7,356th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Honda Civic Coupe 1.6i 105
Year1996
Power103 hp (77 kW)
Kerb mass1,000 kg
Power to weight103 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia 2000 Coupe 2.0 12519719.29 s17.09 s82.4 mph123 bhp
Infiniti M30 Coupe 3.0 V6 16219909.18 s17.18 s86.8 mph160 bhp
Peugeot 504 Coupe 2.7 V6 14319749.29 s17.10 s82.3 mph137 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

0-60 under 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Honda 0-60 timesevery modelFastest coupes911 carsFastest cars of the 1990s2,649 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 Civic Coupe 1.6i 105 0-60 time?
The Honda Civic Coupe 1.6i 105 reaches 60 mph in 9.25 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,861st quickest of the 14,946 cars in the set.
What is the Honda Civic Coupe 1.6i 105 quarter mile time?
17.29 s at 84.9 mph. It reaches the eighth mile in 11.46 s and clears the first 60 ft in 3.06 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Civic Coupe 1.6i 105 have?
103 bhp and 1,000 kg, which is 103 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Civic Coupe 1.6i 105?
Closest here on pace: Lancia 2000 Coupe 2.0 125 (9.29 s), Infiniti M30 Coupe 3.0 V6 162 (9.18 s), Peugeot 504 Coupe 2.7 V6 143 (9.29 s). Each one can be raced against the Honda Civic Coupe 1.6i 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 Honda Civic Coupe 1.6i 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.