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

Mazda 3 / Axela Sedan 2.0i 151

The Mazda 3 / Axela Sedan 2.0i 151 reaches 60 mph in 9.49 s (100 km/h in 10.02 s) and covers a standing quarter mile in 17.17 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.98 s and the eighth mile in 11.26 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 Sedan 2.0i 151 Lancia Thema 2.0 146

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 Sedan 2.0i 151
0–60 mph9.49 s
0–100 km/h10.02 s
0–100 mph—
60 ft2.98 s
1/8 mile11.26 s
1/4 mile17.17 s
Trap speed83.2 mph

About the 3 / Axela Sedan 2.0i 151

The 2009 Mazda 3 / Axela Sedan 2.0i 151 is a front-drive naturally aspirated saloon of 1,245 kg with 149 bhp, which works out at 120 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.98 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 9,264th quickest to 60 mph, and the 107th quickest of the 201 Mazdas here. It traps higher than its 0-60 suggests — 83.2 mph, the 8,215th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Mazda 3 / Axela Sedan 2.0i 151
Year2009
Power149 hp (111 kW)
Kerb mass1,245 kg
Power to weight120 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed128 mph (206 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Thema 2.0 14619889.49 s17.18 s82.9 mph143 bhp
Jaguar XJ 4.2 20819799.39 s17.13 s82.8 mph205 bhp
Lincoln Town Car 4.6 V8 LONG 23920089.38 s17.29 s87.1 mph239 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 saloon cars3,808 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 Sedan 2.0i 151 0-60 time?
The Mazda 3 / Axela Sedan 2.0i 151 reaches 60 mph in 9.49 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,264th quickest of the 14,946 cars in the set.
What is the Mazda 3 / Axela Sedan 2.0i 151 quarter mile time?
17.17 s at 83.2 mph. It reaches the eighth mile in 11.26 s and clears the first 60 ft in 2.98 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mazda 3 / Axela Sedan 2.0i 151 have?
149 bhp and 1,245 kg, which is 120 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 206 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mazda 3 / Axela Sedan 2.0i 151?
Closest here on pace: Lancia Thema 2.0 146 (9.49 s), Jaguar XJ 4.2 208 (9.39 s), Lincoln Town Car 4.6 V8 LONG 239 (9.38 s). Each one can be raced against the Mazda 3 / Axela Sedan 2.0i 151 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 Sedan 2.0i 151 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.