← My Auto Racer All cars Mercedes-Benz 0-60 Comparisons Answers
The Mercedes-Benz S 300 BlueTEC HYBRID reaches 60 mph in 6.97 s and covers a standing quarter mile in 15.38 s, tripping the lights at 89.9 mph. It clears the first 60 ft in 2.35 s and the eighth mile in 9.85 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 | Mercedes-Benz S 300 BlueTEC HYBRID |
|---|---|
| 0–60 mph | 6.97 s |
| 0–100 mph | — |
| 60 ft | 2.35 s |
| 1/8 mile | 9.85 s |
| 1/4 mile | 15.38 s |
| Trap speed | 89.9 mph |
The 2013 Mercedes-Benz S 300 BlueTEC HYBRID is a rear-drive turbodiesel saloon of 2,015 kg with 228 bhp, which works out at 113 bhp per tonne. Rear drive and 113 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.35 s. Against the 2,939 cars in the set it is the 2,363rd quickest to 60 mph, and the 211th quickest of the 255 Mercedes-Benzs here. Its 89.9 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 10 published acceleration figures for this car.
| Specification | Mercedes-Benz S 300 BlueTEC HYBRID |
|---|---|
| Year | 2013 |
| Power | 228 bhp |
| Kerb mass | 2,015 kg |
| Power to weight | 113 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 240 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Volvo V60 D4 190 | 2015 | 6.97 s | 15.35 s | 93.0 mph | 188 bhp |
| BMW 520d (G30) | 2017 | 6.77 s | 15.15 s | 92.3 mph | 188 bhp |
| BMW 320d (F30) | 2012 | 6.81 s | 15.13 s | 95.2 mph | 181 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.