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

Chrysler Voyager 3.8 V6 217

The Chrysler Voyager 3.8 V6 217 reaches 60 mph in 10.06 s (100 km/h in 10.61 s) and covers a standing quarter mile in 17.91 s, tripping the lights at 81.6 mph. It clears the first 60 ft in 3.18 s and the eighth mile in 11.85 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 Voyager 3.8 V6 217 Toyota Yaris Verso 1.5 VVTi 106 (2003)

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 Voyager 3.8 V6 217
0–60 mph10.06 s
0–100 km/h10.61 s
0–100 mph—
60 ft3.18 s
1/8 mile11.85 s
1/4 mile17.91 s
Trap speed81.6 mph

About the Voyager 3.8 V6 217

The 2000 Chrysler Voyager 3.8 V6 217 is a front-drive naturally aspirated MPV of 2,005 kg with 215 bhp, which works out at 107 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.18 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 10,278th quickest to 60 mph, and the 58th quickest of the 76 Chryslers here. It traps higher than its 0-60 suggests — 81.6 mph, the 9,173rd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Chrysler Voyager 3.8 V6 217
Year2000
Power215 hp (160 kW)
Kerb mass2,005 kg
Power to weight107 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota Yaris Verso 1.5 VVTi 106 (2003)200310.28 s17.82 s78.5 mph105 bhp
Toyota Previa 2.4 VVT-i 156 (2003)200310.03 s17.61 s80.1 mph154 bhp
Citroen Berlingo 1.6i 108199610.18 s17.78 s78.5 mph107 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 MPVs and people carriers478 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 Voyager 3.8 V6 217 0-60 time?
The Chrysler Voyager 3.8 V6 217 reaches 60 mph in 10.06 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,278th quickest of the 14,946 cars in the set.
What is the Chrysler Voyager 3.8 V6 217 quarter mile time?
17.91 s at 81.6 mph. It reaches the eighth mile in 11.85 s and clears the first 60 ft in 3.18 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler Voyager 3.8 V6 217 have?
215 bhp and 2,005 kg, which is 107 bhp per tonne. It is front-drive, naturally aspirated, with 4 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 Voyager 3.8 V6 217?
Closest here on pace: Toyota Yaris Verso 1.5 VVTi 106 (2003) (10.28 s), Toyota Previa 2.4 VVT-i 156 (2003) (10.03 s), Citroen Berlingo 1.6i 108 (10.18 s). Each one can be raced against the Chrysler Voyager 3.8 V6 217 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 Voyager 3.8 V6 217 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.