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

VW Beetle 2.0 TDI BlueMotion 150

The VW Beetle 2.0 TDI BlueMotion 150 reaches 60 mph in 7.60 s (100 km/h in 8.54 s) and covers a standing quarter mile in 16.00 s, tripping the lights at 87.2 mph. It clears the first 60 ft in 2.46 s and the eighth mile in 10.35 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 Beetle 2.0 TDI BlueMotion 150 BMW 118i (F40)

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 Beetle 2.0 TDI BlueMotion 150
0–60 mph7.60 s
0–100 km/h8.54 s
0–100 mph—
60 ft2.46 s
1/8 mile10.35 s
1/4 mile16.00 s
Trap speed87.2 mph

About the Beetle 2.0 TDI BlueMotion 150

The 2012 VW Beetle 2.0 TDI BlueMotion 150 is a front-drive turbodiesel car of 1,421 kg with 148 bhp, which works out at 104 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.46 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,743rd quickest to 60 mph, and the 265th quickest of the 1124 VWs here. Its 87.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 2 of 2 published acceleration figures for this car.

On paper

Specification VW Beetle 2.0 TDI BlueMotion 150
Year2012
Power148 hp (110 kW)
Kerb mass1,421 kg
Power to weight104 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed126 mph (203 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
BMW 118i (F40)20197.64 s15.97 s87.0 mph138 bhp
Infiniti Q30 2.2d 17020157.58 s15.84 s85.2 mph168 bhp
Opel Astra 2.0 CDTI Ecotec20097.74 s16.05 s86.8 mph158 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 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 diesel cars4,019 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 Beetle 2.0 TDI BlueMotion 150 0-60 time?
The VW Beetle 2.0 TDI BlueMotion 150 reaches 60 mph in 7.60 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,743rd quickest of the 14,946 cars in the set.
What is the VW Beetle 2.0 TDI BlueMotion 150 quarter mile time?
16.00 s at 87.2 mph. It reaches the eighth mile in 10.35 s and clears the first 60 ft in 2.46 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the VW Beetle 2.0 TDI BlueMotion 150 have?
148 bhp and 1,421 kg, which is 104 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 203 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the VW Beetle 2.0 TDI BlueMotion 150?
Closest here on pace: BMW 118i (F40) (7.64 s), Infiniti Q30 2.2d 170 (7.58 s), Opel Astra 2.0 CDTI Ecotec (7.74 s). Each one can be raced against the VW Beetle 2.0 TDI BlueMotion 150 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 Beetle 2.0 TDI BlueMotion 150 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.