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

Mazda CX-5 2.0 SKYACTIV-G 165

The Mazda CX-5 2.0 SKYACTIV-G 165 reaches 60 mph in 7.71 s (100 km/h in 8.63 s) and covers a standing quarter mile in 16.14 s, tripping the lights at 87.5 mph. It clears the first 60 ft in 2.57 s and the eighth mile in 10.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.

Mazda CX-5 2.0 SKYACTIV-G 165 Renault Captur 1.3 TCe 154

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.0 SKYACTIV-G 165
0–60 mph7.71 s
0–100 km/h8.63 s
0–100 mph—
60 ft2.57 s
1/8 mile10.51 s
1/4 mile16.14 s
Trap speed87.5 mph

About the CX-5 2.0 SKYACTIV-G 165

The 2016 Mazda CX-5 2.0 SKYACTIV-G 165 is a front-drive naturally aspirated SUV of 1,390 kg with 164 bhp, which works out at 118 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.57 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 5,953rd quickest to 60 mph, and the 46th quickest of the 201 Mazdas here. Its 87.5 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 Mazda CX-5 2.0 SKYACTIV-G 165
Year2016
Power164 hp (122 kW)
Kerb mass1,390 kg
Power to weight118 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Captur 1.3 TCe 15420207.75 s16.09 s86.8 mph152 bhp
SEAT Ateca 1.4 TSI 15020167.70 s16.10 s87.5 mph148 bhp
Buick Envision Plus 552T MHEV 21420217.78 s16.09 s87.0 mph211 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 8 seconds6,514 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.0 SKYACTIV-G 165 0-60 time?
The Mazda CX-5 2.0 SKYACTIV-G 165 reaches 60 mph in 7.71 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,953rd quickest of the 14,946 cars in the set.
What is the Mazda CX-5 2.0 SKYACTIV-G 165 quarter mile time?
16.14 s at 87.5 mph. It reaches the eighth mile in 10.51 s and clears the first 60 ft in 2.57 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mazda CX-5 2.0 SKYACTIV-G 165 have?
164 bhp and 1,390 kg, which is 118 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mazda CX-5 2.0 SKYACTIV-G 165?
Closest here on pace: Renault Captur 1.3 TCe 154 (7.75 s), SEAT Ateca 1.4 TSI 150 (7.70 s), Buick Envision Plus 552T MHEV 214 (7.78 s). Each one can be raced against the Mazda CX-5 2.0 SKYACTIV-G 165 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.0 SKYACTIV-G 165 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.