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

Audi A3 1.8 TFSI 160 DCT

The Audi A3 1.8 TFSI 160 DCT reaches 60 mph in 6.75 s (100 km/h in 7.14 s) and covers a standing quarter mile in 15.25 s, tripping the lights at 92.0 mph. It clears the first 60 ft in 2.47 s and the eighth mile in 9.90 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.

Audi A3 1.8 TFSI 160 DCT Mercedes-Benz A-Class (W176) 220d 177

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 Audi A3 1.8 TFSI 160 DCT
0–60 mph6.75 s
0–100 km/h7.14 s
0–100 mph—
60 ft2.47 s
1/8 mile9.90 s
1/4 mile15.25 s
Trap speed92.0 mph

About the A3 1.8 TFSI 160 DCT

The 2008 Audi A3 1.8 TFSI 160 DCT is a front-drive turbocharged car of 1,295 kg with 158 bhp, which works out at 122 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.47 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 4,242nd quickest to 60 mph, and the 512th quickest of the 1320 Audis here. Its 92.0 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 2 of 2 published acceleration figures for this car.

On paper

Specification Audi A3 1.8 TFSI 160 DCT
Year2008
Power158 hp (118 kW)
Kerb mass1,295 kg
Power to weight122 bhp/t
DrivetrainFront drive
Gears7
EngineTurbocharged
Top speed138 mph (222 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-Benz A-Class (W176) 220d 17720156.75 s15.24 s92.4 mph174 bhp
BMW 1 Series 3-door (F21) 118i 17020126.66 s15.26 s91.8 mph168 bhp
Mercedes-Benz B-Class (W246) 220 4MATIC 18320156.71 s15.15 s89.6 mph181 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 8 seconds5,602 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Audi 0-60 timesevery modelFastest hatchbacks4,513 carsFastest cars of the 2000s5,138 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 Audi A3 1.8 TFSI 160 DCT 0-60 time?
The Audi A3 1.8 TFSI 160 DCT reaches 60 mph in 6.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,242nd quickest of the 14,946 cars in the set.
What is the Audi A3 1.8 TFSI 160 DCT quarter mile time?
15.25 s at 92.0 mph. It reaches the eighth mile in 9.90 s and clears the first 60 ft in 2.47 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Audi A3 1.8 TFSI 160 DCT have?
158 bhp and 1,295 kg, which is 122 bhp per tonne. It is front-drive, turbocharged, with 7 gears and a quoted top speed of 222 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Audi A3 1.8 TFSI 160 DCT?
Closest here on pace: Mercedes-Benz A-Class (W176) 220d 177 (6.75 s), BMW 1 Series 3-door (F21) 118i 170 (6.66 s), Mercedes-Benz B-Class (W246) 220 4MATIC 183 (6.71 s). Each one can be raced against the Audi A3 1.8 TFSI 160 DCT 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 Audi A3 1.8 TFSI 160 DCT 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.