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

BMW X3 3.0d 218 (2007)

The BMW X3 3.0d 218 (2007) reaches 60 mph in 6.65 s (100 km/h in 7.06 s) and covers a standing quarter mile in 15.14 s, tripping the lights at 88.9 mph. It clears the first 60 ft in 2.14 s and the eighth mile in 9.65 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.

BMW X3 3.0d 218 (2007) VW Touareg 5.0 V10 TDI 310

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 BMW X3 3.0d 218 (2007)
0–60 mph6.65 s
0–100 km/h7.06 s
0–100 mph—
60 ft2.14 s
1/8 mile9.65 s
1/4 mile15.14 s
Trap speed88.9 mph

About the X3 3.0d 218

The 2007 BMW X3 3.0d 218 (2007) is an all-wheel-drive turbodiesel SUV of 1,780 kg with 215 bhp, which works out at 121 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.14 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 4,098th quickest to 60 mph, and the 569th quickest of the 1324 BMWs here. It leaves better than it pulls: 88.9 mph at the lights is only the 5,589th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification BMW X3 3.0d 218 (2007)
Year2007
Power215 hp (160 kW)
Kerb mass1,780 kg
Power to weight121 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed137 mph (220 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
VW Touareg 5.0 V10 TDI 31020076.63 s15.13 s90.7 mph308 bhp
Mercedes-Benz ML-Class (W166) 350 BlueTEC 4MATIC 25820116.62 s15.08 s89.9 mph255 bhp
VW Touareg 3.0 TDI SCR V6 23420196.70 s15.16 s89.3 mph231 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
BMW 0-60 timesevery modelFastest SUVs2,049 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 BMW X3 3.0d 218 (2007) 0-60 time?
The BMW X3 3.0d 218 (2007) reaches 60 mph in 6.65 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,098th quickest of the 14,946 cars in the set.
What is the BMW X3 3.0d 218 (2007) quarter mile time?
15.14 s at 88.9 mph. It reaches the eighth mile in 9.65 s and clears the first 60 ft in 2.14 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW X3 3.0d 218 (2007) have?
215 bhp and 1,780 kg, which is 121 bhp per tonne. It is all-wheel-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 BMW X3 3.0d 218 (2007)?
Closest here on pace: VW Touareg 5.0 V10 TDI 310 (6.63 s), Mercedes-Benz ML-Class (W166) 350 BlueTEC 4MATIC 258 (6.62 s), VW Touareg 3.0 TDI SCR V6 234 (6.70 s). Each one can be raced against the BMW X3 3.0d 218 (2007) 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 BMW X3 3.0d 218 (2007) 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.