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

VW Golf GTD 5dr 2.0 TDI 170 DCT

The VW Golf GTD 5dr 2.0 TDI 170 DCT reaches 60 mph in 7.28 s (100 km/h in 7.74 s) and covers a standing quarter mile in 15.70 s, tripping the lights at 88.6 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 10.13 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.

VW Golf GTD 5dr 2.0 TDI 170 DCT Skoda Octavia 1.8 TSI 1Z

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 VW Golf GTD 5dr 2.0 TDI 170 DCT
0–60 mph7.28 s
0–100 km/h7.74 s
0–100 mph—
60 ft2.49 s
1/8 mile10.13 s
1/4 mile15.70 s
Trap speed88.6 mph

About the Golf GTD 5dr 2.0 TDI 170 DCT

The 2009 VW Golf GTD 5dr 2.0 TDI 170 DCT is a front-drive turbodiesel car of 1,431 kg with 168 bhp, which works out at 117 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.49 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 5,141st quickest to 60 mph, and the 207th quickest of the 1124 VWs here. Its 88.6 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 VW Golf GTD 5dr 2.0 TDI 170 DCT
Year2009
Power168 hp (125 kW)
Kerb mass1,431 kg
Power to weight117 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed137 mph (220 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Octavia 1.8 TSI 1Z20087.27 s15.68 s89.7 mph158 bhp
Alfa Romeo MiTo 1.4 14020167.28 s15.73 s88.2 mph138 bhp
MINI Hatch Cooper SD 2.0 14320067.27 s15.74 s88.1 mph141 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 8 seconds6,514 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
VW 0-60 timesevery modelFastest diesel cars4,019 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 VW Golf GTD 5dr 2.0 TDI 170 DCT 0-60 time?
The VW Golf GTD 5dr 2.0 TDI 170 DCT reaches 60 mph in 7.28 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,141st quickest of the 14,946 cars in the set.
What is the VW Golf GTD 5dr 2.0 TDI 170 DCT quarter mile time?
15.70 s at 88.6 mph. It reaches the eighth mile in 10.13 s and clears the first 60 ft in 2.49 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the VW Golf GTD 5dr 2.0 TDI 170 DCT have?
168 bhp and 1,431 kg, which is 117 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 220 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the VW Golf GTD 5dr 2.0 TDI 170 DCT?
Closest here on pace: Skoda Octavia 1.8 TSI 1Z (7.27 s), Alfa Romeo MiTo 1.4 140 (7.28 s), MINI Hatch Cooper SD 2.0 143 (7.27 s). Each one can be raced against the VW Golf GTD 5dr 2.0 TDI 170 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 VW Golf GTD 5dr 2.0 TDI 170 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.