← My Auto Racer All cars Toyota 0-60 Comparisons
The Toyota GR Supra Mk V 340 PS reaches 60 mph in 3.97 s and covers a standing quarter mile in 12.52 s, tripping the lights at 110.4 mph. It clears the first 60 ft in 1.96 s and the eighth mile in 8.07 s, reaching 100 mph in 9.98 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 | Toyota GR Supra Mk V 340 PS |
|---|---|
| 0–60 mph | 3.97 s |
| 0–100 mph | 9.98 s |
| 60 ft | 1.96 s |
| 1/8 mile | 8.07 s |
| 1/4 mile | 12.52 s |
| Trap speed | 110.4 mph |
The 2019 Toyota GR Supra Mk V 340 PS is a rear-drive turbocharged coupe of 1,541 kg with 335 bhp, which works out at 218 bhp per tonne. Rear drive and 218 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.96 s. Against the 2,929 cars in the set it is the 777th quickest to 60 mph, and the 3rd quickest of the 45 Toyotas here. It leaves better than it pulls: 110.4 mph at the lights is only the 1,006th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Toyota GR Supra Mk V 340 PS |
|---|---|
| Year | 2019 |
| Power | 335 bhp |
| Kerb mass | 1,541 kg |
| Power to weight | 218 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 262 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Audi S6 | 2019 | 4.00 s | 12.53 s | 109.4 mph | 444 bhp |
| Audi S5 B10 | 2025 | 3.98 s | 12.57 s | 107.7 mph | 362 bhp |
| Alpine A110 Mk II | 2017 | 3.96 s | 12.52 s | 110.5 mph | 248 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.