← My Auto Racer All cars TVR 0-60 Comparisons
The TVR Sagaris reaches 60 mph in 3.36 s and covers a standing quarter mile in 11.67 s, tripping the lights at 120.3 mph. It clears the first 60 ft in 1.82 s and the eighth mile in 7.57 s, reaching 100 mph in 8.17 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 | TVR Sagaris |
|---|---|
| 0–60 mph | 3.36 s |
| 0–100 mph | 8.17 s |
| 60 ft | 1.82 s |
| 1/8 mile | 7.57 s |
| 1/4 mile | 11.67 s |
| Trap speed | 120.3 mph |
The 2003 TVR Sagaris is a rear-drive naturally aspirated supercar of 1,078 kg with 394 bhp, which works out at 366 bhp per tonne. Rear drive and 366 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.82 s. Against the 2,929 cars in the set it is the 414th quickest to 60 mph, inside the fastest quarter, and the quickest of the 14 TVRs here. Its 120.3 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 5 of 5 published acceleration figures for this car.
| Specification | TVR Sagaris |
|---|---|
| Year | 2003 |
| Power | 394 bhp |
| Kerb mass | 1,078 kg |
| Power to weight | 366 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 298 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lotus Exige 410 Sport Mk III | 2018 | 3.36 s | 11.82 s | 115.9 mph | 410 bhp |
| Superformance Le Mans Coupe V8 | 2007 | 3.37 s | 11.42 s | 126.6 mph | 510 bhp |
| Aston Martin Vanquish S Mk II | 2016 | 3.28 s | 11.57 s | 120.1 mph | 595 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.