← My Auto Racer All cars Brabus 0-60 Comparisons
The Brabus Bodo reaches 60 mph in 2.50 s and covers a standing quarter mile in 10.21 s, tripping the lights at 138.8 mph. It clears the first 60 ft in 1.65 s and the eighth mile in 6.64 s, reaching 100 mph in 5.44 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 | Brabus Bodo |
|---|---|
| 0–60 mph | 2.50 s |
| 0–100 mph | 5.44 s |
| 60 ft | 1.65 s |
| 1/8 mile | 6.64 s |
| 1/4 mile | 10.21 s |
| Trap speed | 138.8 mph |
The 2026 Brabus Bodo is a rear-drive turbocharged supercar of 1,910 kg with 986 bhp, which works out at 516 bhp per tonne. Rear drive and 516 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.65 s. Against the 2,929 cars in the set it is the 66th quickest to 60 mph, inside the fastest five per cent, and the 5th quickest of the 24 Brabuss here. Its 138.8 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 9 of 11 published acceleration figures for this car.
| Specification | Brabus Bodo |
|---|---|
| Year | 2026 |
| Power | 986 bhp |
| Kerb mass | 1,910 kg |
| Power to weight | 516 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 360 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lamborghini Centenario LP770-4 Roadster | 2017 | 2.53 s | 10.20 s | 138.6 mph | 759 bhp |
| Lamborghini Aventador LP750-4 SV | 2016 | 2.55 s | 10.26 s | 137.7 mph | 740 bhp |
| Ferrari Monza SP1 | 2018 | 2.53 s | 10.00 s | 143.6 mph | 799 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.