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

Chrysler Voyager 2.5 CRD 141

The Chrysler Voyager 2.5 CRD 141 reaches 60 mph in 10.79 s (100 km/h in 11.47 s) and covers a standing quarter mile in 18.28 s, tripping the lights at 78.4 mph. It clears the first 60 ft in 3.21 s and the eighth mile in 11.96 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 2.5 CRD 141 Lancia Voyager 2.8 163

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 2.5 CRD 141
0–60 mph10.79 s
0–100 km/h11.47 s
0–100 mph—
60 ft3.21 s
1/8 mile11.96 s
1/4 mile18.28 s
Trap speed78.4 mph

About the Voyager 2.5 CRD 141

The 2000 Chrysler Voyager 2.5 CRD 141 is a front-drive turbodiesel MPV of 1,995 kg with 139 bhp, which works out at 70 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.21 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 11,360th quickest to 60 mph, and the 65th quickest of the 76 Chryslers here. Its 78.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 Chrysler Voyager 2.5 CRD 141
Year2000
Power139 hp (104 kW)
Kerb mass1,995 kg
Power to weight70 bhp/t
DrivetrainFront drive
Gears4
EngineTurbodiesel
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Voyager 2.8 163201110.75 s17.85 s77.2 mph161 bhp
Peugeot Tepee Partner 1.6 VTi 120 BVM5200810.93 s18.22 s77.3 mph118 bhp
Vauxhall Meriva 1.7 CDTi 110 (2010)201010.72 s17.82 s76.8 mph109 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 2.5 CRD 141 0-60 time?
The Chrysler Voyager 2.5 CRD 141 reaches 60 mph in 10.79 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,360th quickest of the 14,946 cars in the set.
What is the Chrysler Voyager 2.5 CRD 141 quarter mile time?
18.28 s at 78.4 mph. It reaches the eighth mile in 11.96 s and clears the first 60 ft in 3.21 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler Voyager 2.5 CRD 141 have?
139 bhp and 1,995 kg, which is 70 bhp per tonne. It is front-drive, turbodiesel, with 4 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chrysler Voyager 2.5 CRD 141?
Closest here on pace: Lancia Voyager 2.8 163 (10.75 s), Peugeot Tepee Partner 1.6 VTi 120 BVM5 (10.93 s), Vauxhall Meriva 1.7 CDTi 110 (2010) (10.72 s). Each one can be raced against the Chrysler Voyager 2.5 CRD 141 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 2.5 CRD 141 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.