← My Auto Racer All cars Chrysler 0-60 Comparisons
The Chrysler 300C SRT8 Mk I reaches 60 mph in 4.30 s and covers a standing quarter mile in 12.96 s, tripping the lights at 109.8 mph. It clears the first 60 ft in 2.04 s and the eighth mile in 8.38 s, reaching 100 mph in 10.94 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Chrysler 300C SRT8 Mk I |
|---|---|
| 0–60 mph | 4.30 s |
| 0–100 mph | 10.94 s |
| 60 ft | 2.04 s |
| 1/8 mile | 8.38 s |
| 1/4 mile | 12.96 s |
| Trap speed | 109.8 mph |
The 2005 Chrysler 300C SRT8 Mk I is a rear-drive naturally aspirated saloon of 1,910 kg with 425 bhp, which works out at 223 bhp per tonne. Rear drive and 223 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.04 s. Against the 2,929 cars in the set it is the 965th quickest to 60 mph, and the 2nd quickest of the 11 Chryslers here. Its 109.8 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 9 of 10 published acceleration figures for this car.
| Specification | Chrysler 300C SRT8 Mk I |
|---|---|
| Year | 2005 |
| Power | 425 bhp |
| Kerb mass | 1,910 kg |
| Power to weight | 223 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 282 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lexus IS F | 2007 | 4.31 s | 12.86 s | 111.1 mph | 417 bhp |
| Kia EV9 GT | 2025 | 4.29 s | 12.88 s | 108.1 mph | 502 bhp |
| Infiniti Q60 3.0t | 2016 | 4.53 s | 13.07 s | 105.9 mph | 400 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.