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

Mazda CX-5 2.0 Skyactiv-G 160

The Mazda CX-5 2.0 Skyactiv-G 160 reaches 60 mph in 9.38 s (100 km/h in 10.49 s) and covers a standing quarter mile in 17.13 s, tripping the lights at 80.2 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 10.94 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 160 Hyundai Santa Fe 2.4 185

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 160
0–60 mph9.38 s
0–100 km/h10.49 s
0–100 mph—
60 ft2.49 s
1/8 mile10.94 s
1/4 mile17.13 s
Trap speed80.2 mph

About the CX-5 2.0 Skyactiv-G 160

The 2016 Mazda CX-5 2.0 Skyactiv-G 160 is an all-wheel-drive turbocharged SUV of 1,420 kg with 158 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.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 9,078th quickest to 60 mph, and the 100th quickest of the 201 Mazdas here. Its 80.2 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 160
Year2016
Power158 hp (118 kW)
Kerb mass1,420 kg
Power to weight111 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbocharged
Top speed123 mph (198 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Santa Fe 2.4 18520189.37 s17.12 s81.0 mph182 bhp
Hyundai Bayon 1.0 TGD-i 48V 12020229.36 s17.08 s79.9 mph118 bhp
Kia Sorento 2.4 18520189.46 s17.18 s80.9 mph182 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 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 160 0-60 time?
The Mazda CX-5 2.0 Skyactiv-G 160 reaches 60 mph in 9.38 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,078th quickest of the 14,946 cars in the set.
What is the Mazda CX-5 2.0 Skyactiv-G 160 quarter mile time?
17.13 s at 80.2 mph. It reaches the eighth mile in 10.94 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.0 Skyactiv-G 160 have?
158 bhp and 1,420 kg, which is 111 bhp per tonne. It is all-wheel-drive, turbocharged, with 6 gears and a quoted top speed of 198 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 160?
Closest here on pace: Hyundai Santa Fe 2.4 185 (9.37 s), Hyundai Bayon 1.0 TGD-i 48V 120 (9.36 s), Kia Sorento 2.4 185 (9.46 s). Each one can be raced against the Mazda CX-5 2.0 Skyactiv-G 160 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 160 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.