← My Auto Racer All cars BMW 0-60 Comparisons
The BMW M135i F20 reaches 60 mph in 4.76 s and covers a standing quarter mile in 13.10 s, tripping the lights at 106.7 mph. It clears the first 60 ft in 2.00 s and the eighth mile in 8.49 s, reaching 100 mph in 11.06 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 M135i F20 |
|---|---|
| 0–60 mph | 4.76 s |
| 0–100 mph | 11.06 s |
| 60 ft | 2.00 s |
| 1/8 mile | 8.49 s |
| 1/4 mile | 13.10 s |
| Trap speed | 106.7 mph |
The 2012 BMW M135i F20 is a rear-drive turbocharged car of 1,440 kg with 315 bhp, which works out at 219 bhp per tonne. Rear drive and 219 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.00 s. Against the 2,929 cars in the set it is the 1,250th quickest to 60 mph, and the 120th quickest of the 297 BMWs here. Its 106.7 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 | BMW M135i F20 |
|---|---|
| Year | 2012 |
| Power | 315 bhp |
| Kerb mass | 1,440 kg |
| Power to weight | 219 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Cupra Leon VZ TCR Edition | 2026 | 4.74 s | 13.13 s | 110.2 mph | 321 bhp |
| Chrysler Crossfire SRT-6 | 2005 | 4.73 s | 13.08 s | 105.5 mph | 330 bhp |
| Subaru Impreza 22B STI Version | 1998 | 4.80 s | 13.20 s | 103.8 mph | 276 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.