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

Chrysler Aspen 5.7 V8 2WD 335

The Chrysler Aspen 5.7 V8 2WD 335 reaches 60 mph in 6.77 s (100 km/h in 7.16 s) and covers a standing quarter mile in 15.32 s, tripping the lights at 90.5 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 9.88 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.

Chrysler Aspen 5.7 V8 2WD 335 Land Rover Range Rover Sport 4.2 V8 SC 390

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 Chrysler Aspen 5.7 V8 2WD 335
0–60 mph6.77 s
0–100 km/h7.16 s
0–100 mph—
60 ft2.49 s
1/8 mile9.88 s
1/4 mile15.32 s
Trap speed90.5 mph

About the Aspen 5.7 V8 2WD 335

The 2006 Chrysler Aspen 5.7 V8 2WD 335 is a rear-drive naturally aspirated SUV of 2,227 kg with 335 bhp, which works out at 151 bhp per tonne. Rear drive and 151 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.49 s. Against the 14,946 cars in the set it is the 4,270th quickest to 60 mph, and the 19th quickest of the 76 Chryslers here. Its 90.5 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 Chrysler Aspen 5.7 V8 2WD 335
Year2006
Power335 hp (250 kW)
Kerb mass2,227 kg
Power to weight151 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Range Rover Sport 4.2 V8 SC 39020056.80 s15.29 s89.5 mph390 bhp
Land Rover Discovery Sport 2.0 Si4 29020146.79 s15.24 s88.7 mph286 bhp
Lexus LX 570 V8 38320126.76 s15.28 s90.7 mph384 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
Chrysler 0-60 timesevery modelFastest SUVs2,049 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 Chrysler Aspen 5.7 V8 2WD 335 0-60 time?
The Chrysler Aspen 5.7 V8 2WD 335 reaches 60 mph in 6.77 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,270th quickest of the 14,946 cars in the set.
What is the Chrysler Aspen 5.7 V8 2WD 335 quarter mile time?
15.32 s at 90.5 mph. It reaches the eighth mile in 9.88 s and clears the first 60 ft in 2.49 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler Aspen 5.7 V8 2WD 335 have?
335 bhp and 2,227 kg, which is 151 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chrysler Aspen 5.7 V8 2WD 335?
Closest here on pace: Land Rover Range Rover Sport 4.2 V8 SC 390 (6.80 s), Land Rover Discovery Sport 2.0 Si4 290 (6.79 s), Lexus LX 570 V8 383 (6.76 s). Each one can be raced against the Chrysler Aspen 5.7 V8 2WD 335 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 Chrysler Aspen 5.7 V8 2WD 335 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.