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

Acura Acua TLX 3.5 V6 294

The Acura Acua TLX 3.5 V6 294 reaches 60 mph in 6.18 s (100 km/h in 6.57 s) and covers a standing quarter mile in 14.85 s, tripping the lights at 90.6 mph. It clears the first 60 ft in 2.14 s and the eighth mile in 9.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.

Acura Acua TLX 3.5 V6 294 Lexus ES 350 276

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 Acua TLX 3.5 V6 294
0–60 mph6.18 s
0–100 km/h6.57 s
0–100 mph—
60 ft2.14 s
1/8 mile9.43 s
1/4 mile14.85 s
Trap speed90.6 mph

About the Acua TLX 3.5 V6 294

The 2015 Acura Acua TLX 3.5 V6 294 is an all-wheel-drive naturally aspirated saloon of 1,700 kg with 290 bhp, which works out at 170 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.14 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 3,458th quickest to 60 mph, inside the fastest quarter, and the 7th quickest of the 25 Acuras here. It leaves better than it pulls: 90.6 mph at the lights is only the 4,918th 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 Acura Acua TLX 3.5 V6 294
Year2015
Power290 hp (216 kW)
Kerb mass1,700 kg
Power to weight170 bhp/t
DrivetrainAll-wheel drive
Gears9
EngineNaturally aspirated
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lexus ES 350 27620066.16 s14.61 s99.0 mph272 bhp
Toyota Camry V620086.29 s14.77 s96.2 mph268 bhp
Lexus LS 400 V8 28419976.26 s14.72 s99.0 mph280 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 7 seconds4,651 cars0-100 km/h under 7 seconds4,031 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 4x4s and all-wheel-drive cars2,981 carsFastest cars of the 2010s4,541 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 Acua TLX 3.5 V6 294 0-60 time?
The Acura Acua TLX 3.5 V6 294 reaches 60 mph in 6.18 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,458th quickest of the 14,946 cars in the set.
What is the Acura Acua TLX 3.5 V6 294 quarter mile time?
14.85 s at 90.6 mph. It reaches the eighth mile in 9.43 s and clears the first 60 ft in 2.14 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Acura Acua TLX 3.5 V6 294 have?
290 bhp and 1,700 kg, which is 170 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 9 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Acura Acua TLX 3.5 V6 294?
Closest here on pace: Lexus ES 350 276 (6.16 s), Toyota Camry V6 (6.29 s), Lexus LS 400 V8 284 (6.26 s). Each one can be raced against the Acura Acua TLX 3.5 V6 294 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 Acua TLX 3.5 V6 294 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.