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

Acura Legend 2.5 V6 151

The Acura Legend 2.5 V6 151 reaches 60 mph in 9.30 s (100 km/h in 9.83 s) and covers a standing quarter mile in 17.04 s, tripping the lights at 83.9 mph. It clears the first 60 ft in 2.95 s and the eighth mile in 11.18 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.

Acura Legend 2.5 V6 151 Kia Optima / Magentis 2.0 16V 144

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 Acura Legend 2.5 V6 151
0–60 mph9.30 s
0–100 km/h9.83 s
0–100 mph—
60 ft2.95 s
1/8 mile11.18 s
1/4 mile17.04 s
Trap speed83.9 mph

About the Legend 2.5 V6 151

The 1986 Acura Legend 2.5 V6 151 is a front-drive naturally aspirated saloon of 1,396 kg with 150 bhp, which works out at 108 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.95 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,972nd quickest to 60 mph, and the 24th quickest of the 25 Acuras here. It traps higher than its 0-60 suggests — 83.9 mph, the 7,889th 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 Acura Legend 2.5 V6 151
Year1986
Power150 hp (112 kW)
Kerb mass1,396 kg
Power to weight108 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed129 mph (208 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Kia Optima / Magentis 2.0 16V 14420069.30 s17.04 s83.9 mph142 bhp
Holden Cruze 1.4 Turbo 14020089.32 s17.11 s80.7 mph138 bhp
Hyundai Sonata 2.0i 5MTFWD 13919949.30 s17.07 s82.8 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
Acura 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 1980s1,057 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 Acura Legend 2.5 V6 151 0-60 time?
The Acura Legend 2.5 V6 151 reaches 60 mph in 9.30 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,972nd quickest of the 14,946 cars in the set.
What is the Acura Legend 2.5 V6 151 quarter mile time?
17.04 s at 83.9 mph. It reaches the eighth mile in 11.18 s and clears the first 60 ft in 2.95 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Acura Legend 2.5 V6 151 have?
150 bhp and 1,396 kg, which is 108 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 208 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Acura Legend 2.5 V6 151?
Closest here on pace: Kia Optima / Magentis 2.0 16V 144 (9.30 s), Holden Cruze 1.4 Turbo 140 (9.32 s), Hyundai Sonata 2.0i 5MTFWD 139 (9.30 s). Each one can be raced against the Acura Legend 2.5 V6 151 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 Acura Legend 2.5 V6 151 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.