← My Auto Racer All cars BMW 0-60 Comparisons
The BMW M140i reaches 60 mph in 3.90 s and covers a standing quarter mile in 12.38 s, tripping the lights at 111.0 mph. It clears the first 60 ft in 1.91 s and the eighth mile in 7.94 s, reaching 100 mph in 9.72 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 | BMW M140i |
|---|---|
| 0–60 mph | 3.90 s |
| 0–100 mph | 9.72 s |
| 60 ft | 1.91 s |
| 1/8 mile | 7.94 s |
| 1/4 mile | 12.38 s |
| Trap speed | 111.0 mph |
The 2016 BMW M140i is a rear-drive turbocharged car of 1,475 kg with 335 bhp, which works out at 227 bhp per tonne. Rear drive and 227 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.91 s. Against the 2,929 cars in the set it is the 731st quickest to 60 mph, inside the fastest quarter, and the 62nd quickest of the 297 BMWs here. It leaves better than it pulls: 111.0 mph at the lights is only the 956th 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 | BMW M140i |
|---|---|
| Year | 2016 |
| Power | 335 bhp |
| Kerb mass | 1,475 kg |
| Power to weight | 227 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Alpine A110 Mk II | 2017 | 3.96 s | 12.52 s | 110.5 mph | 248 bhp |
| VW Golf R MK VIII facelift | 2025 | 3.98 s | 12.55 s | 110.2 mph | 329 bhp |
| Lotus Evora 400 | 2016 | 3.96 s | 12.33 s | 115.0 mph | 400 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.