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

Honda Accord CC7 2.2i VTEC 150

The Honda Accord CC7 2.2i VTEC 150 reaches 60 mph in 9.66 s (100 km/h in 10.14 s) and covers a standing quarter mile in 17.51 s, tripping the lights at 86.1 mph. It clears the first 60 ft in 3.09 s and the eighth mile in 11.75 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 CC7 2.2i VTEC 150 Hyundai Sonata 2.0 165

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 CC7 2.2i VTEC 150
0–60 mph9.66 s
0–100 km/h10.14 s
0–100 mph—
60 ft3.09 s
1/8 mile11.75 s
1/4 mile17.51 s
Trap speed86.1 mph

About the Accord CC7 2.2i VTEC 150

The 1993 Honda Accord CC7 2.2i VTEC 150 is a front-drive naturally aspirated saloon of 1,305 kg with 148 bhp, which works out at 113 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.09 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 9,558th quickest to 60 mph, and the 106th quickest of the 191 Hondas here. It traps higher than its 0-60 suggests — 86.1 mph, the 6,810th 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 CC7 2.2i VTEC 150
Year1993
Power148 hp (110 kW)
Kerb mass1,305 kg
Power to weight113 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Sonata 2.0 16520119.65 s17.44 s81.0 mph162 bhp
Saab 9000 CS 2.3i 15019919.65 s17.52 s85.6 mph148 bhp
Toyota Camry 2.4 VVT-i 15220019.64 s17.53 s85.1 mph150 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 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 saloon cars3,808 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 CC7 2.2i VTEC 150 0-60 time?
The Honda Accord CC7 2.2i VTEC 150 reaches 60 mph in 9.66 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,558th quickest of the 14,946 cars in the set.
What is the Honda Accord CC7 2.2i VTEC 150 quarter mile time?
17.51 s at 86.1 mph. It reaches the eighth mile in 11.75 s and clears the first 60 ft in 3.09 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Accord CC7 2.2i VTEC 150 have?
148 bhp and 1,305 kg, which is 113 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Accord CC7 2.2i VTEC 150?
Closest here on pace: Hyundai Sonata 2.0 165 (9.65 s), Saab 9000 CS 2.3i 150 (9.65 s), Toyota Camry 2.4 VVT-i 152 (9.64 s). Each one can be raced against the Honda Accord CC7 2.2i VTEC 150 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 CC7 2.2i VTEC 150 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.