← My Auto Racer All cars Chrysler 0-60 Comparisons
The Chrysler Crossfire SRT-6 reaches 60 mph in 4.73 s and covers a standing quarter mile in 13.08 s, tripping the lights at 105.5 mph. It clears the first 60 ft in 1.97 s and the eighth mile in 8.44 s, reaching 100 mph in 11.21 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 Crossfire SRT-6 |
|---|---|
| 0–60 mph | 4.73 s |
| 0–100 mph | 11.21 s |
| 60 ft | 1.97 s |
| 1/8 mile | 8.44 s |
| 1/4 mile | 13.08 s |
| Trap speed | 105.5 mph |
The 2005 Chrysler Crossfire SRT-6 is a rear-drive turbocharged car of 1,459 kg with 330 bhp, which works out at 226 bhp per tonne. Rear drive and 226 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.97 s. Against the 2,929 cars in the set it is the 1,236th quickest to 60 mph, and the 4th quickest of the 11 Chryslers here. Its 105.5 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 Crossfire SRT-6 |
|---|---|
| Year | 2005 |
| Power | 330 bhp |
| Kerb mass | 1,459 kg |
| Power to weight | 226 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 255 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Cupra Leon VZ TCR Edition | 2026 | 4.74 s | 13.13 s | 110.2 mph | 321 bhp |
| BMW M135i F20 | 2012 | 4.76 s | 13.10 s | 106.7 mph | 315 bhp |
| Subaru Impreza 22B STI Version | 1998 | 4.80 s | 13.20 s | 103.8 mph | 276 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.