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

Dodge Avenger 3.5 V6 238

The Dodge Avenger 3.5 V6 238 reaches 60 mph in 6.77 s (100 km/h in 7.16 s) and covers a standing quarter mile in 15.24 s, tripping the lights at 92.4 mph. It clears the first 60 ft in 2.48 s and the eighth mile in 9.86 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 Avenger 3.5 V6 238 Saab 9000 CS 2.3 Turbo 200

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 Avenger 3.5 V6 238
0–60 mph6.77 s
0–100 km/h7.16 s
0–100 mph—
60 ft2.48 s
1/8 mile9.86 s
1/4 mile15.24 s
Trap speed92.4 mph

About the Avenger 3.5 V6 238

The 2007 Dodge Avenger 3.5 V6 238 is an all-wheel-drive naturally aspirated saloon of 1,696 kg with 235 bhp, which works out at 138 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.48 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 4,273rd quickest to 60 mph, and the 37th quickest of the 60 Dodges here. Its 92.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 Dodge Avenger 3.5 V6 238
Year2007
Power235 hp (175 kW)
Kerb mass1,696 kg
Power to weight138 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineNaturally aspirated
Top speed143 mph (230 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Saab 9000 CS 2.3 Turbo 20019916.79 s15.20 s95.1 mph197 bhp
Lexus SC 300 22819916.73 s15.20 s94.8 mph225 bhp
Lexus GS 200t 24420166.86 s15.26 s91.5 mph241 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 7 seconds4,651 cars0-100 km/h under 8 seconds5,602 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 4x4s and all-wheel-drive cars2,981 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 Avenger 3.5 V6 238 0-60 time?
The Dodge Avenger 3.5 V6 238 reaches 60 mph in 6.77 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,273rd quickest of the 14,946 cars in the set.
What is the Dodge Avenger 3.5 V6 238 quarter mile time?
15.24 s at 92.4 mph. It reaches the eighth mile in 9.86 s and clears the first 60 ft in 2.48 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dodge Avenger 3.5 V6 238 have?
235 bhp and 1,696 kg, which is 138 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 6 gears and a quoted top speed of 230 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dodge Avenger 3.5 V6 238?
Closest here on pace: Saab 9000 CS 2.3 Turbo 200 (6.79 s), Lexus SC 300 228 (6.73 s), Lexus GS 200t 244 (6.86 s). Each one can be raced against the Dodge Avenger 3.5 V6 238 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 Avenger 3.5 V6 238 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.