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

Dodge Neon 2.0 SMPI 133

The Dodge Neon 2.0 SMPI 133 reaches 60 mph in 8.19 s (100 km/h in 8.64 s) and covers a standing quarter mile in 16.25 s, tripping the lights at 87.0 mph. It clears the first 60 ft in 2.73 s and the eighth mile in 10.58 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.

Dodge Neon 2.0 SMPI 133 Mazda 3/Axela Hatchback 2.0 150

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 Dodge Neon 2.0 SMPI 133
0–60 mph8.19 s
0–100 km/h8.64 s
0–100 mph—
60 ft2.73 s
1/8 mile10.58 s
1/4 mile16.25 s
Trap speed87.0 mph

About the Neon 2.0 SMPI 133

The 2003 Dodge Neon 2.0 SMPI 133 is a front-drive naturally aspirated car of 1,171 kg with 131 bhp, which works out at 112 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.73 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 6,891st quickest to 60 mph, and the 40th quickest of the 60 Dodges here. Its 87.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 Dodge Neon 2.0 SMPI 133
Year2003
Power131 hp (98 kW)
Kerb mass1,171 kg
Power to weight112 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda 3/Axela Hatchback 2.0 15020048.19 s16.25 s87.0 mph148 bhp
Opel Corsa 3dr 1.8 GSi 12520008.19 s16.24 s87.2 mph123 bhp
Toyota Yaris 5dr 1.5 16V VVT-i 10620038.19 s16.31 s86.1 mph105 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
Dodge 0-60 timesevery modelFastest hatchbacks4,513 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 Dodge Neon 2.0 SMPI 133 0-60 time?
The Dodge Neon 2.0 SMPI 133 reaches 60 mph in 8.19 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,891st quickest of the 14,946 cars in the set.
What is the Dodge Neon 2.0 SMPI 133 quarter mile time?
16.25 s at 87.0 mph. It reaches the eighth mile in 10.58 s and clears the first 60 ft in 2.73 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dodge Neon 2.0 SMPI 133 have?
131 bhp and 1,171 kg, which is 112 bhp per tonne. It is front-drive, naturally aspirated, with 5 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 Dodge Neon 2.0 SMPI 133?
Closest here on pace: Mazda 3/Axela Hatchback 2.0 150 (8.19 s), Opel Corsa 3dr 1.8 GSi 125 (8.19 s), Toyota Yaris 5dr 1.5 16V VVT-i 106 (8.19 s). Each one can be raced against the Dodge Neon 2.0 SMPI 133 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 Dodge Neon 2.0 SMPI 133 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.