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

VW Golf GTD 3dr 2.0 TDI 170

The VW Golf GTD 3dr 2.0 TDI 170 reaches 60 mph in 7.34 s (100 km/h in 7.74 s) and covers a standing quarter mile in 15.68 s, tripping the lights at 89.9 mph. It clears the first 60 ft in 2.47 s and the eighth mile in 10.18 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 3dr 2.0 TDI 170 Peugeot 207 - 5dr 1.6 THP 156

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 3dr 2.0 TDI 170
0–60 mph7.34 s
0–100 km/h7.74 s
0–100 mph—
60 ft2.47 s
1/8 mile10.18 s
1/4 mile15.68 s
Trap speed89.9 mph

About the Golf GTD 3dr 2.0 TDI 170

The 2009 VW Golf GTD 3dr 2.0 TDI 170 is a front-drive turbodiesel car of 1,409 kg with 168 bhp, which works out at 119 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 5,237th quickest to 60 mph, and the 216th quickest of the 1124 VWs here. Its 89.9 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 3dr 2.0 TDI 170
Year2009
Power168 hp (125 kW)
Kerb mass1,409 kg
Power to weight119 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed138 mph (222 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot 207 - 5dr 1.6 THP 15620097.33 s15.76 s89.0 mph148 bhp
Ford Mondeo Hatchback 2.2 Duratorq TDCi 20020077.35 s15.64 s91.2 mph197 bhp
Mercedes-Benz A-Class (W176) 200 15620157.34 s15.66 s90.8 mph154 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 3dr 2.0 TDI 170 0-60 time?
The VW Golf GTD 3dr 2.0 TDI 170 reaches 60 mph in 7.34 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,237th quickest of the 14,946 cars in the set.
What is the VW Golf GTD 3dr 2.0 TDI 170 quarter mile time?
15.68 s at 89.9 mph. It reaches the eighth mile in 10.18 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 VW Golf GTD 3dr 2.0 TDI 170 have?
168 bhp and 1,409 kg, which is 119 bhp per tonne. It is front-drive, turbodiesel, with 6 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 VW Golf GTD 3dr 2.0 TDI 170?
Closest here on pace: Peugeot 207 - 5dr 1.6 THP 156 (7.33 s), Ford Mondeo Hatchback 2.2 Duratorq TDCi 200 (7.35 s), Mercedes-Benz A-Class (W176) 200 156 (7.34 s). Each one can be raced against the VW Golf GTD 3dr 2.0 TDI 170 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 3dr 2.0 TDI 170 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.