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

Chrysler 300C 3.0 V6 CRD 215

The Chrysler 300C 3.0 V6 CRD 215 reaches 60 mph in 6.83 s (100 km/h in 7.25 s) and covers a standing quarter mile in 15.37 s, tripping the lights at 90.6 mph. It clears the first 60 ft in 2.53 s and the eighth mile in 9.95 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 300C 3.0 V6 CRD 215 Audi A4 2.7 TDI CVT 190

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 300C 3.0 V6 CRD 215
0–60 mph6.83 s
0–100 km/h7.25 s
0–100 mph—
60 ft2.53 s
1/8 mile9.95 s
1/4 mile15.37 s
Trap speed90.6 mph

About the 300C 3.0 V6 CRD 215

The 2004 Chrysler 300C 3.0 V6 CRD 215 is a rear-drive turbodiesel saloon of 1,835 kg with 215 bhp, which works out at 117 bhp per tonne. Rear drive and 117 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.53 s. Against the 14,946 cars in the set it is the 4,386th quickest to 60 mph, and the 21st quickest of the 76 Chryslers here. Its 90.6 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 300C 3.0 V6 CRD 215
Year2004
Power215 hp (160 kW)
Kerb mass1,835 kg
Power to weight117 bhp/t
DrivetrainRear drive
Gears5
EngineTurbodiesel
Top speed143 mph (230 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Audi A4 2.7 TDI CVT 19020076.89 s15.40 s89.6 mph188 bhp
Mercedes-Benz E-Class (W211) 280 CDI V6 4MATIC 19020026.84 s15.36 s91.8 mph188 bhp
BMW 3 Series (F30) 328d 18420126.86 s15.26 s91.5 mph181 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 saloon cars3,808 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 300C 3.0 V6 CRD 215 0-60 time?
The Chrysler 300C 3.0 V6 CRD 215 reaches 60 mph in 6.83 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,386th quickest of the 14,946 cars in the set.
What is the Chrysler 300C 3.0 V6 CRD 215 quarter mile time?
15.37 s at 90.6 mph. It reaches the eighth mile in 9.95 s and clears the first 60 ft in 2.53 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chrysler 300C 3.0 V6 CRD 215 have?
215 bhp and 1,835 kg, which is 117 bhp per tonne. It is rear-drive, turbodiesel, with 5 gears and a quoted top speed of 230 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chrysler 300C 3.0 V6 CRD 215?
Closest here on pace: Audi A4 2.7 TDI CVT 190 (6.89 s), Mercedes-Benz E-Class (W211) 280 CDI V6 4MATIC 190 (6.84 s), BMW 3 Series (F30) 328d 184 (6.86 s). Each one can be raced against the Chrysler 300C 3.0 V6 CRD 215 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 300C 3.0 V6 CRD 215 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.