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

Mazda CX-3 2.0 120

The Mazda CX-3 2.0 120 reaches 60 mph in 8.64 s (100 km/h in 9.21 s) and covers a standing quarter mile in 16.62 s, tripping the lights at 83.0 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 10.69 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-3 2.0 120 Toyota Auris 5dr 2.0D 124

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-3 2.0 120
0–60 mph8.64 s
0–100 km/h9.21 s
0–100 mph—
60 ft2.64 s
1/8 mile10.69 s
1/4 mile16.62 s
Trap speed83.0 mph

About the CX-3 2.0 120

The 2015 Mazda CX-3 2.0 120 is an all-wheel-drive naturally aspirated car of 1,340 kg with 118 bhp, which works out at 88 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.64 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 7,769th quickest to 60 mph, and the 75th quickest of the 201 Mazdas here. Its 83.0 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-3 2.0 120
Year2015
Power118 hp (88 kW)
Kerb mass1,340 kg
Power to weight88 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineNaturally aspirated
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota Auris 5dr 2.0D 12420138.59 s16.69 s82.3 mph122 bhp
Land Rover Range Rover Evoque 5dr 2.2 TD4 15020118.61 s16.54 s81.0 mph148 bhp
Alfa Romeo 147 (5dr) 1.9 JTD 12020058.71 s16.61 s83.0 mph118 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 4x4s and all-wheel-drive cars2,981 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-3 2.0 120 0-60 time?
The Mazda CX-3 2.0 120 reaches 60 mph in 8.64 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,769th quickest of the 14,946 cars in the set.
What is the Mazda CX-3 2.0 120 quarter mile time?
16.62 s at 83.0 mph. It reaches the eighth mile in 10.69 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 Mazda CX-3 2.0 120 have?
118 bhp and 1,340 kg, which is 88 bhp per tonne. It is all-wheel-drive, naturally aspirated, 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-3 2.0 120?
Closest here on pace: Toyota Auris 5dr 2.0D 124 (8.59 s), Land Rover Range Rover Evoque 5dr 2.2 TD4 150 (8.61 s), Alfa Romeo 147 (5dr) 1.9 JTD 120 (8.71 s). Each one can be raced against the Mazda CX-3 2.0 120 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-3 2.0 120 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.