← My Auto Racer All cars Audi 0-60 Comparisons Answers
The Audi A4 2.0 TDI B9 reaches 60 mph in 6.94 s and covers a standing quarter mile in 15.36 s, tripping the lights at 90.2 mph. It clears the first 60 ft in 2.36 s and the eighth mile in 9.84 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 | Audi A4 2.0 TDI B9 |
|---|---|
| 0–60 mph | 6.94 s |
| 0–100 mph | — |
| 60 ft | 2.36 s |
| 1/8 mile | 9.84 s |
| 1/4 mile | 15.36 s |
| Trap speed | 90.2 mph |
The 2015 Audi A4 2.0 TDI B9 is a front-drive turbodiesel car of 1,590 kg with 188 bhp, which works out at 118 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.36 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,353rd quickest to 60 mph, and the 220th quickest of the 261 Audis here. Its 90.2 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 10 published acceleration figures for this car.
| Specification | Audi A4 2.0 TDI B9 |
|---|---|
| Year | 2015 |
| Power | 188 bhp |
| Kerb mass | 1,590 kg |
| Power to weight | 118 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 240 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| SEAT Leon FR TDI | 2007 | 6.87 s | 15.39 s | 91.1 mph | 168 bhp |
| Mercedes-Benz E 220 D W213 | 2016 | 6.89 s | 15.25 s | 95.1 mph | 192 bhp |
| BMW 120d Edition Sport | 2010 | 7.02 s | 15.46 s | 90.0 mph | 174 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.