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

Mazda CX-5 2.2D 150

The Mazda CX-5 2.2D 150 reaches 60 mph in 9.18 s (100 km/h in 9.78 s) and covers a standing quarter mile in 16.85 s, tripping the lights at 80.2 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 10.73 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.

Mazda CX-5 2.2D 150 Land Rover Defender 90 2.0 SD4 200

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 Mazda CX-5 2.2D 150
0–60 mph9.18 s
0–100 km/h9.78 s
0–100 mph—
60 ft2.49 s
1/8 mile10.73 s
1/4 mile16.85 s
Trap speed80.2 mph

About the CX-5 2.2D 150

The 2012 Mazda CX-5 2.2D 150 is an all-wheel-drive turbodiesel SUV of 1,615 kg with 148 bhp, which works out at 91 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.49 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 8,743rd quickest to 60 mph, and the 94th quickest of the 201 Mazdas here. It leaves better than it pulls: 80.2 mph at the lights is only the 9,908th 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 Mazda CX-5 2.2D 150
Year2012
Power148 hp (110 kW)
Kerb mass1,615 kg
Power to weight91 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Defender 90 2.0 SD4 20020199.14 s16.83 s78.9 mph197 bhp
Volkswagen T-Roc 1.0 TSI 11520179.20 s16.89 s81.9 mph114 bhp
Jeep Wrangler Unlimited Rubicon JL 2.2 CRD 20020189.18 s16.94 s77.5 mph197 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 10 seconds10,136 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
Mazda 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 Mazda CX-5 2.2D 150 0-60 time?
The Mazda CX-5 2.2D 150 reaches 60 mph in 9.18 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,743rd quickest of the 14,946 cars in the set.
What is the Mazda CX-5 2.2D 150 quarter mile time?
16.85 s at 80.2 mph. It reaches the eighth mile in 10.73 s and clears the first 60 ft in 2.49 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mazda CX-5 2.2D 150 have?
148 bhp and 1,615 kg, which is 91 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mazda CX-5 2.2D 150?
Closest here on pace: Land Rover Defender 90 2.0 SD4 200 (9.14 s), Volkswagen T-Roc 1.0 TSI 115 (9.20 s), Jeep Wrangler Unlimited Rubicon JL 2.2 CRD 200 (9.18 s). Each one can be raced against the Mazda CX-5 2.2D 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 Mazda CX-5 2.2D 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.