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

Chrysler Town and Country 2.4 147

The Chrysler Town and Country 2.4 147 reaches 60 mph in 14.46 s (100 km/h in 15.32 s) and covers a standing quarter mile in 20.26 s, tripping the lights at 72.0 mph. It clears the first 60 ft in 3.62 s and the eighth mile in 13.38 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 Town and Country 2.4 147 Land Rover Range Rover 2.5 D 136

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 Town and Country 2.4 147
0–60 mph14.46 s
0–100 km/h15.32 s
0–100 mph—
60 ft3.62 s
1/8 mile13.38 s
1/4 mile20.26 s
Trap speed72.0 mph

About the Town and Country 2.4 147

The 2000 Chrysler Town and Country 2.4 147 is a front-drive naturally aspirated SUV of 1,935 kg with 145 bhp, which works out at 75 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.62 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 14,273rd quickest to 60 mph, and the 76th quickest of the 76 Chryslers here. Its 72.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 Chrysler Town and Country 2.4 147
Year2000
Power145 hp (108 kW)
Kerb mass1,935 kg
Power to weight75 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed114 mph (183 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Range Rover 2.5 D 136199414.40 s20.42 s71.8 mph134 bhp
VW Cross Up! 1.0 75201614.45 s20.28 s70.6 mph74 bhp
Lada Samara 3dr 1.3 65198614.57 s20.25 s70.8 mph64 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

Slower 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 Town and Country 2.4 147 0-60 time?
The Chrysler Town and Country 2.4 147 reaches 60 mph in 14.46 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,273rd quickest of the 14,946 cars in the set.
What is the Chrysler Town and Country 2.4 147 quarter mile time?
20.26 s at 72.0 mph. It reaches the eighth mile in 13.38 s and clears the first 60 ft in 3.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler Town and Country 2.4 147 have?
145 bhp and 1,935 kg, which is 75 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 183 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chrysler Town and Country 2.4 147?
Closest here on pace: Land Rover Range Rover 2.5 D 136 (14.40 s), VW Cross Up! 1.0 75 (14.45 s), Lada Samara 3dr 1.3 65 (14.57 s). Each one can be raced against the Chrysler Town and Country 2.4 147 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 Town and Country 2.4 147 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.