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

BMW X5 xDrive 35d 265

The BMW X5 xDrive 35d 265 reaches 60 mph in 6.36 s (100 km/h in 6.76 s) and covers a standing quarter mile in 14.88 s, tripping the lights at 92.6 mph. It clears the first 60 ft in 2.24 s and the eighth mile in 9.51 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 X5 xDrive 35d 265 Mercedes-Benz GLE (W166) 350 d 4MATIC 258

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 X5 xDrive 35d 265
0–60 mph6.36 s
0–100 km/h6.76 s
0–100 mph—
60 ft2.24 s
1/8 mile9.51 s
1/4 mile14.88 s
Trap speed92.6 mph

About the X5 xDrive 35d 265

The 2010 BMW X5 xDrive 35d 265 is an all-wheel-drive turbodiesel SUV of 2,355 kg with 261 bhp, which works out at 111 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.24 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 3,710th quickest to 60 mph, inside the fastest quarter, and the 522nd quickest of the 1324 BMWs here. Its 92.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 BMW X5 xDrive 35d 265
Year2010
Power261 hp (195 kW)
Kerb mass2,355 kg
Power to weight111 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed150 mph (241 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-Benz GLE (W166) 350 d 4MATIC 25820156.35 s14.86 s91.2 mph255 bhp
Mercedes-Benz GLE 300d 4MATIC 24520206.44 s14.93 s90.8 mph241 bhp
Mercedes-Benz GLA (X156) 220 4MATIC 18320176.33 s14.87 s90.9 mph181 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 7 seconds4,031 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 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 BMW X5 xDrive 35d 265 0-60 time?
The BMW X5 xDrive 35d 265 reaches 60 mph in 6.36 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,710th quickest of the 14,946 cars in the set.
What is the BMW X5 xDrive 35d 265 quarter mile time?
14.88 s at 92.6 mph. It reaches the eighth mile in 9.51 s and clears the first 60 ft in 2.24 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW X5 xDrive 35d 265 have?
261 bhp and 2,355 kg, which is 111 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 241 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the BMW X5 xDrive 35d 265?
Closest here on pace: Mercedes-Benz GLE (W166) 350 d 4MATIC 258 (6.35 s), Mercedes-Benz GLE 300d 4MATIC 245 (6.44 s), Mercedes-Benz GLA (X156) 220 4MATIC 183 (6.33 s). Each one can be raced against the BMW X5 xDrive 35d 265 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 X5 xDrive 35d 265 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.