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

Honda Accord Coupe 2.0 136

The Honda Accord Coupe 2.0 136 reaches 60 mph in 11.04 s (100 km/h in 11.61 s) and covers a standing quarter mile in 18.53 s, tripping the lights at 81.4 mph. It clears the first 60 ft in 3.28 s and the eighth mile in 12.45 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 Accord Coupe 2.0 136 Isuzu 117 Coupe 1.8 105

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 Accord Coupe 2.0 136
0–60 mph11.04 s
0–100 km/h11.61 s
0–100 mph—
60 ft3.28 s
1/8 mile12.45 s
1/4 mile18.53 s
Trap speed81.4 mph

About the Accord Coupe 2.0 136

The 1994 Honda Accord Coupe 2.0 136 is a front-drive naturally aspirated coupe of 1,315 kg with 134 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.28 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,738th quickest to 60 mph, and the 146th quickest of the 191 Hondas here. It traps higher than its 0-60 suggests — 81.4 mph, the 9,241st 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 Accord Coupe 2.0 136
Year1994
Power134 hp (100 kW)
Kerb mass1,315 kg
Power to weight102 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed123 mph (198 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Isuzu 117 Coupe 1.8 105196811.02 s18.28 s76.9 mph103 bhp
Vauxhall Astra 5dr 1.8 125200411.02 s18.54 s80.4 mph123 bhp
Holden Astra Coupe 1.8 125200510.76 s18.32 s80.8 mph123 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

Honda Accord Coupe 2.0 136 vs Ford Escape 2.0 126Full 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 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 Accord Coupe 2.0 136 0-60 time?
The Honda Accord Coupe 2.0 136 reaches 60 mph in 11.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,738th quickest of the 14,946 cars in the set.
What is the Honda Accord Coupe 2.0 136 quarter mile time?
18.53 s at 81.4 mph. It reaches the eighth mile in 12.45 s and clears the first 60 ft in 3.28 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Accord Coupe 2.0 136 have?
134 bhp and 1,315 kg, which is 102 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 198 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Accord Coupe 2.0 136?
Closest here on pace: Isuzu 117 Coupe 1.8 105 (11.02 s), Vauxhall Astra 5dr 1.8 125 (11.02 s), Holden Astra Coupe 1.8 125 (10.76 s). Each one can be raced against the Honda Accord Coupe 2.0 136 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 Accord Coupe 2.0 136 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.