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

VW Jetta 2.0TDI DSG Mk VI

The VW Jetta 2.0TDI DSG Mk VI reaches 60 mph in 8.57 s (100 km/h in 9.07 s) and covers a standing quarter mile in 16.67 s, tripping the lights at 86.2 mph. It clears the first 60 ft in 2.77 s and the eighth mile in 10.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.

VW Jetta 2.0TDI DSG Mk VI Renault Mégane Hatch 1.9 dCi 130

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 Jetta 2.0TDI DSG Mk VI
0–60 mph8.57 s
0–100 km/h9.07 s
0–100 mph—
60 ft2.77 s
1/8 mile10.90 s
1/4 mile16.67 s
Trap speed86.2 mph

About the Jetta 2.0TDI DSG Mk VI

The 2011 VW Jetta 2.0TDI DSG Mk VI is a front-drive turbocharged car of 1,369 kg with 138 bhp, which works out at 101 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.77 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 7,623rd quickest to 60 mph, and the 468th quickest of the 1124 VWs here. Its 86.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 9 published acceleration figures for this car.

On paper

Specification VW Jetta 2.0TDI DSG Mk VI
Year2011
Power138 hp (103 kW)
Kerb mass1,369 kg
Power to weight101 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed138 mph (222 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Mégane Hatch 1.9 dCi 13020088.57 s16.65 s82.9 mph129 bhp
Opel Astra 5dr 1.4 ECOTEC Start/Stop 12520158.57 s16.65 s82.4 mph123 bhp
Ford Focus 1.0 EcoBoost 125 (Mk4)20188.59 s16.70 s82.4 mph123 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 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 hatchbacks4,513 carsFastest cars of the 2010s4,541 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 Jetta 2.0TDI DSG Mk VI 0-60 time?
The VW Jetta 2.0TDI DSG Mk VI reaches 60 mph in 8.57 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,623rd quickest of the 14,946 cars in the set.
What is the VW Jetta 2.0TDI DSG Mk VI quarter mile time?
16.67 s at 86.2 mph. It reaches the eighth mile in 10.90 s and clears the first 60 ft in 2.77 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the VW Jetta 2.0TDI DSG Mk VI have?
138 bhp and 1,369 kg, which is 101 bhp per tonne. It is front-drive, turbocharged, 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 Jetta 2.0TDI DSG Mk VI?
Closest here on pace: Renault Mégane Hatch 1.9 dCi 130 (8.57 s), Opel Astra 5dr 1.4 ECOTEC Start/Stop 125 (8.57 s), Ford Focus 1.0 EcoBoost 125 (Mk4) (8.59 s). Each one can be raced against the VW Jetta 2.0TDI DSG Mk VI 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 Jetta 2.0TDI DSG Mk VI is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 9 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.