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

Chrysler Aspen 4.7 V8 235

The Chrysler Aspen 4.7 V8 235 reaches 60 mph in 9.79 s (100 km/h in 10.40 s) and covers a standing quarter mile in 17.55 s, tripping the lights at 80.1 mph. It clears the first 60 ft in 3.00 s and the eighth mile in 11.41 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 4.7 V8 235 Daihatsu Materia 1.5 103

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 4.7 V8 235
0–60 mph9.79 s
0–100 km/h10.40 s
0–100 mph—
60 ft3.00 s
1/8 mile11.41 s
1/4 mile17.55 s
Trap speed80.1 mph

About the Aspen 4.7 V8 235

The 2006 Chrysler Aspen 4.7 V8 235 is an all-wheel-drive naturally aspirated SUV of 2,278 kg with 235 bhp, which works out at 103 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.00 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 9,761st quickest to 60 mph, and the 53rd quickest of the 76 Chryslers here. Its 80.1 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 4.7 V8 235
Year2006
Power235 hp (175 kW)
Kerb mass2,278 kg
Power to weight103 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Daihatsu Materia 1.5 10320079.81 s17.56 s79.2 mph102 bhp
Mitsubishi Pajero/Montero/Shogun SWB 3.8 V6 25020069.81 s17.55 s82.0 mph247 bhp
Mazda 5 / Premacy 2.0 14520059.85 s17.45 s81.4 mph143 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
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 4.7 V8 235 0-60 time?
The Chrysler Aspen 4.7 V8 235 reaches 60 mph in 9.79 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,761st quickest of the 14,946 cars in the set.
What is the Chrysler Aspen 4.7 V8 235 quarter mile time?
17.55 s at 80.1 mph. It reaches the eighth mile in 11.41 s and clears the first 60 ft in 3.00 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler Aspen 4.7 V8 235 have?
235 bhp and 2,278 kg, which is 103 bhp per tonne. It is all-wheel-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 4.7 V8 235?
Closest here on pace: Daihatsu Materia 1.5 103 (9.81 s), Mitsubishi Pajero/Montero/Shogun SWB 3.8 V6 250 (9.81 s), Mazda 5 / Premacy 2.0 145 (9.85 s). Each one can be raced against the Chrysler Aspen 4.7 V8 235 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 4.7 V8 235 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.