← My Auto Racer All cars Acura 0-60 Comparisons
The Acura TL reaches 60 mph in 5.78 s and covers a standing quarter mile in 14.35 s, tripping the lights at 97.5 mph. It clears the first 60 ft in 2.30 s and the eighth mile in 9.26 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Acura TL |
|---|---|
| 0–60 mph | 5.78 s |
| 0–100 mph | — |
| 60 ft | 2.30 s |
| 1/8 mile | 9.26 s |
| 1/4 mile | 14.35 s |
| Trap speed | 97.5 mph |
The 2009 Acura TL is an all-wheel-drive naturally aspirated saloon of 1,705 kg with 304 bhp, which works out at 179 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.30 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 2,929 cars in the set it is the 1,843rd quickest to 60 mph, and the 2nd quickest of the 5 Acuras here. Its 97.5 mph trap speed sits about where its 0-60 puts it, so it launches and pulls in roughly equal measure. The simulation is trimmed to 9 of 9 published acceleration figures for this car.
| Specification | Acura TL |
|---|---|
| Year | 2009 |
| Power | 304 bhp |
| Kerb mass | 1,705 kg |
| Power to weight | 179 bhp/t |
| Drivetrain | All-wheel drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 242 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Audi A6 4.2 quattro | 2007 | 5.72 s | 14.26 s | 98.8 mph | 330 bhp |
| Volvo S60 T6 | 2010 | 5.74 s | 14.21 s | 100.1 mph | 300 bhp |
| Audi A5 3.2 8T3 | 2007 | 5.68 s | 14.22 s | 99.0 mph | 261 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.