← My Auto Racer All cars Mercedes-Benz 0-60 Comparisons Answers

Mercedes-Benz X-Class 220d 163

The Mercedes-Benz X-Class 220d 163 reaches 60 mph in 11.31 s (100 km/h in 12.06 s) and covers a standing quarter mile in 18.18 s, tripping the lights at 74.7 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 11.60 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.

Mercedes-Benz X-Class 220d 163 Dacia Jogger 1.0 TCe EGO-G 101

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 Mercedes-Benz X-Class 220d 163
0–60 mph11.31 s
0–100 km/h12.06 s
0–100 mph—
60 ft2.64 s
1/8 mile11.60 s
1/4 mile18.18 s
Trap speed74.7 mph

About the X-Class 220d 163

The 2017 Mercedes-Benz X-Class 220d 163 is a rear-drive turbodiesel pickup of 2,133 kg with 161 bhp, which works out at 75 bhp per tonne. Rear drive and 75 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.64 s. Against the 14,946 cars in the set it is the 12,035th quickest to 60 mph, and the 1,228th quickest of the 1380 Mercedes-Benzs here. Its 74.7 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 Mercedes-Benz X-Class 220d 163
Year2017
Power161 hp (120 kW)
Kerb mass2,133 kg
Power to weight75 bhp/t
DrivetrainRear drive
Gears6
EngineTurbodiesel
Top speed107 mph (172 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dacia Jogger 1.0 TCe EGO-G 101202311.33 s18.21 s75.0 mph90 bhp
Toyota AURIS 1.4 4D 90201811.34 s18.15 s74.9 mph89 bhp
SEAT Altea XL 1.9 TDI 105200911.33 s18.14 s74.8 mph103 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

BMW 320d (G20) vs Mercedes-Benz X-Class 220d 163Full comparison

Where these times sit

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Mercedes-Benz 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 Mercedes-Benz X-Class 220d 163 0-60 time?
The Mercedes-Benz X-Class 220d 163 reaches 60 mph in 11.31 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,035th quickest of the 14,946 cars in the set.
What is the Mercedes-Benz X-Class 220d 163 quarter mile time?
18.18 s at 74.7 mph. It reaches the eighth mile in 11.60 s and clears the first 60 ft in 2.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mercedes-Benz X-Class 220d 163 have?
161 bhp and 2,133 kg, which is 75 bhp per tonne. It is rear-drive, turbodiesel, with 6 gears and a quoted top speed of 172 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mercedes-Benz X-Class 220d 163?
Closest here on pace: Dacia Jogger 1.0 TCe EGO-G 101 (11.33 s), Toyota AURIS 1.4 4D 90 (11.34 s), SEAT Altea XL 1.9 TDI 105 (11.33 s). Each one can be raced against the Mercedes-Benz X-Class 220d 163 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 Mercedes-Benz X-Class 220d 163 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.