← My Auto Racer All cars TVR 0-60 Comparisons Answers
The TVR S3 reaches 60 mph in 6.47 s (100 km/h in 6.77 s) and covers a standing quarter mile in 15.01 s, tripping the lights at 95.4 mph. It clears the first 60 ft in 2.59 s and the eighth mile in 9.86 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 S3 |
|---|---|
| 0–60 mph | 6.47 s |
| 0–100 km/h | 6.77 s |
| 0–100 mph | — |
| 60 ft | 2.59 s |
| 1/8 mile | 9.86 s |
| 1/4 mile | 15.01 s |
| Trap speed | 95.4 mph |
The 1990 TVR S3 is a rear-drive naturally aspirated saloon of 1,020 kg with 169 bhp, which works out at 166 bhp per tonne. Rear drive and 166 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.59 s. Against the 14,946 cars in the set it is the 3,839th quickest to 60 mph, and the 31st quickest of the 32 TVRs here. Its 95.4 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 7 of 9 published acceleration figures for this car.
| Specification | TVR S3 |
|---|---|
| Year | 1990 |
| Power | 169 hp (126 kW) |
| Kerb mass | 1,020 kg |
| Power to weight | 166 bhp/t |
| Drivetrain | Rear drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 144 mph (232 km/h), quoted |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Fisker Karma | 2010 | 6.41 s | 15.00 s | 91.7 mph | 402 bhp |
| Mercury Milan 3.0 V6 Flex Fuel 250 | 2009 | 6.51 s | 15.02 s | 92.8 mph | 249 bhp |
| Volvo C30 T5 230 PS | 2008 | 6.45 s | 14.90 s | 96.1 mph | 227 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-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.