← My Auto Racer All cars Brabham 0-60 Comparisons
The Brabham BT64 reaches 60 mph in 3.51 s and covers a standing quarter mile in 11.54 s, tripping the lights at 126.4 mph. It clears the first 60 ft in 1.89 s and the eighth mile in 7.55 s, reaching 100 mph in 7.43 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 | Brabham BT64 |
|---|---|
| 0–60 mph | 3.51 s |
| 0–100 mph | 7.43 s |
| 60 ft | 1.89 s |
| 1/8 mile | 7.55 s |
| 1/4 mile | 11.54 s |
| Trap speed | 126.4 mph |
The 2009 Brabham BT64 is a rear-drive naturally aspirated supercar of 1,797 kg with 605 bhp, which works out at 337 bhp per tonne. Rear drive and 337 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 517th quickest to 60 mph, inside the fastest quarter. It traps higher than its 0-60 suggests — 126.4 mph, the 296th 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 | Brabham BT64 |
|---|---|
| Year | 2009 |
| Power | 605 bhp |
| Kerb mass | 1,797 kg |
| Power to weight | 337 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 330 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mclaren Mercedes SLR Roadster | 2007 | 3.46 s | 11.32 s | 130.0 mph | 617 bhp |
| TVR Tuscan S Mk II | 2015 | 3.44 s | 11.69 s | 120.2 mph | 394 bhp |
| Jaguar F-type R AWD | 2015 | 3.43 s | 11.63 s | 121.4 mph | 543 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.