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

Mazda 3/Axela Hatchback 1.6 CD 110

The Mazda 3/Axela Hatchback 1.6 CD 110 reaches 60 mph in 10.41 s (100 km/h in 11.07 s) and covers a standing quarter mile in 17.75 s, tripping the lights at 77.4 mph. It clears the first 60 ft in 2.79 s and the eighth mile in 11.38 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 3/Axela Hatchback 1.6 CD 110 DS Automobiles DS3 1.6 HDi 90

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 3/Axela Hatchback 1.6 CD 110
0–60 mph10.41 s
0–100 km/h11.07 s
0–100 mph—
60 ft2.79 s
1/8 mile11.38 s
1/4 mile17.75 s
Trap speed77.4 mph

About the 3/Axela Hatchback 1.6 CD 110

The 2004 Mazda 3/Axela Hatchback 1.6 CD 110 is a front-drive turbodiesel car of 1,240 kg with 109 bhp, which works out at 88 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.79 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 10,815th quickest to 60 mph, and the 143rd quickest of the 201 Mazdas here. Its 77.4 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 3/Axela Hatchback 1.6 CD 110
Year2004
Power109 hp (81 kW)
Kerb mass1,240 kg
Power to weight88 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed113 mph (182 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
DS Automobiles DS3 1.6 HDi 90201410.41 s17.75 s77.4 mph91 bhp
Renault Sandero GT Line 1.6 8v 106201210.45 s17.75 s77.7 mph97 bhp
Kia Pro cee'd 1.4 16V 109200710.40 s17.84 s79.4 mph107 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Mazda 0-60 timesevery modelFastest diesel cars4,019 carsFastest cars of the 2000s5,138 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 3/Axela Hatchback 1.6 CD 110 0-60 time?
The Mazda 3/Axela Hatchback 1.6 CD 110 reaches 60 mph in 10.41 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,815th quickest of the 14,946 cars in the set.
What is the Mazda 3/Axela Hatchback 1.6 CD 110 quarter mile time?
17.75 s at 77.4 mph. It reaches the eighth mile in 11.38 s and clears the first 60 ft in 2.79 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mazda 3/Axela Hatchback 1.6 CD 110 have?
109 bhp and 1,240 kg, which is 88 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 182 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mazda 3/Axela Hatchback 1.6 CD 110?
Closest here on pace: DS Automobiles DS3 1.6 HDi 90 (10.41 s), Renault Sandero GT Line 1.6 8v 106 (10.45 s), Kia Pro cee'd 1.4 16V 109 (10.40 s). Each one can be raced against the Mazda 3/Axela Hatchback 1.6 CD 110 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 3/Axela Hatchback 1.6 CD 110 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.