← My Auto Racer All cars Callaway 0-60 Comparisons
The Callaway LM V8 reaches 60 mph in 3.76 s and covers a standing quarter mile in 12.28 s, tripping the lights at 112.3 mph. It clears the first 60 ft in 1.89 s and the eighth mile in 7.87 s, reaching 100 mph in 9.60 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 | Callaway LM V8 |
|---|---|
| 0–60 mph | 3.76 s |
| 0–100 mph | 9.60 s |
| 60 ft | 1.89 s |
| 1/8 mile | 7.87 s |
| 1/4 mile | 12.28 s |
| Trap speed | 112.3 mph |
The 2015 Callaway LM V8 is a rear-drive naturally aspirated supercar of 1,441 kg with 464 bhp, which works out at 322 bhp per tonne. Rear drive and 322 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.89 s. Against the 2,929 cars in the set it is the 652nd quickest to 60 mph, inside the fastest quarter, and the quickest of the 3 Callaways here. It leaves better than it pulls: 112.3 mph at the lights is only the 896th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 5 of 5 published acceleration figures for this car.
| Specification | Callaway LM V8 |
|---|---|
| Year | 2015 |
| Power | 464 bhp |
| Kerb mass | 1,441 kg |
| Power to weight | 322 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Naturally aspirated |
| Top speed | 297 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| TVR T350T | 2003 | 3.81 s | 12.24 s | 115.2 mph | 349 bhp |
| Ascari Ecosse | 1998 | 3.90 s | 12.25 s | 116.5 mph | 400 bhp |
| Saleen S351 | 2001 | 3.69 s | 12.12 s | 117.2 mph | 488 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.