← My Auto Racer All cars SRT 0-60 Comparisons
The SRT Viper reaches 60 mph in 3.49 s and covers a standing quarter mile in 11.39 s, tripping the lights at 129.2 mph. It clears the first 60 ft in 1.88 s and the eighth mile in 7.48 s, reaching 100 mph in 7.11 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 | SRT Viper |
|---|---|
| 0–60 mph | 3.49 s |
| 0–100 mph | 7.11 s |
| 60 ft | 1.88 s |
| 1/8 mile | 7.48 s |
| 1/4 mile | 11.39 s |
| Trap speed | 129.2 mph |
The 2013 SRT Viper is a rear-drive naturally aspirated supercar of 1,520 kg with 640 bhp, which works out at 421 bhp per tonne. Rear drive and 421 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.88 s. Against the 2,929 cars in the set it is the 497th quickest to 60 mph, inside the fastest quarter. It traps higher than its 0-60 suggests — 129.2 mph, the 233rd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 9 of 11 published acceleration figures for this car.
| Specification | SRT Viper |
|---|---|
| Year | 2013 |
| Power | 640 bhp |
| Kerb mass | 1,520 kg |
| Power to weight | 421 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 332 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Dodge Viper ACR Mk V | 2016 | 3.51 s | 11.48 s | 126.1 mph | 645 bhp |
| Wiesmann GT MF5 Mk II | 2011 | 3.50 s | 11.46 s | 125.5 mph | 547 bhp |
| Isdera Commendatore 112i Mk I facelift | 2003 | 3.65 s | 11.37 s | 129.9 mph | 620 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.