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

BMW X3 3.0d 204

The BMW X3 3.0d 204 reaches 60 mph in 7.09 s (100 km/h in 7.55 s) and covers a standing quarter mile in 15.54 s, tripping the lights at 86.7 mph. It clears the first 60 ft in 2.18 s and the eighth mile in 9.89 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 204 Mercedes-Benz GLK 250 BlueTEC 4MATIC 204

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 204
0–60 mph7.09 s
0–100 km/h7.55 s
0–100 mph—
60 ft2.18 s
1/8 mile9.89 s
1/4 mile15.54 s
Trap speed86.7 mph

About the X3 3.0d 204

The 2004 BMW X3 3.0d 204 is an all-wheel-drive turbodiesel SUV of 1,825 kg with 201 bhp, which works out at 110 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.18 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,843rd quickest to 60 mph, and the 707th quickest of the 1324 BMWs here. It leaves better than it pulls: 86.7 mph at the lights is only the 6,540th 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 204
Year2004
Power201 hp (150 kW)
Kerb mass1,825 kg
Power to weight110 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed130 mph (210 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-Benz GLK 250 BlueTEC 4MATIC 20420127.14 s15.53 s86.2 mph201 bhp
Land Rover Discovery 3.0 V6 TD6 25820177.14 s15.53 s86.2 mph255 bhp
Audi Q3 Facelift 2.0 TDI 18420167.11 s15.49 s88.6 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.

Head to head

Audi A4 1.6 102 vs BMW X3 3.0d 204Full comparison

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
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 204 0-60 time?
The BMW X3 3.0d 204 reaches 60 mph in 7.09 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,843rd quickest of the 14,946 cars in the set.
What is the BMW X3 3.0d 204 quarter mile time?
15.54 s at 86.7 mph. It reaches the eighth mile in 9.89 s and clears the first 60 ft in 2.18 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW X3 3.0d 204 have?
201 bhp and 1,825 kg, which is 110 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 210 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the BMW X3 3.0d 204?
Closest here on pace: Mercedes-Benz GLK 250 BlueTEC 4MATIC 204 (7.14 s), Land Rover Discovery 3.0 V6 TD6 258 (7.14 s), Audi Q3 Facelift 2.0 TDI 184 (7.11 s). Each one can be raced against the BMW X3 3.0d 204 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 204 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.