← My Auto Racer All cars Marcos 0-60 Comparisons
The Marcos LM500 reaches 60 mph in 4.17 s and covers a standing quarter mile in 12.92 s, tripping the lights at 105.1 mph. It clears the first 60 ft in 1.93 s and the eighth mile in 8.22 s, reaching 100 mph in 11.52 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 | Marcos LM500 |
|---|---|
| 0–60 mph | 4.17 s |
| 0–100 mph | 11.52 s |
| 60 ft | 1.93 s |
| 1/8 mile | 8.22 s |
| 1/4 mile | 12.92 s |
| Trap speed | 105.1 mph |
The 2015 Marcos LM500 is a rear-drive naturally aspirated car of 1,103 kg with 321 bhp, which works out at 291 bhp per tonne. Rear drive and 291 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.93 s. Against the 2,929 cars in the set it is the 898th quickest to 60 mph, and the 3rd quickest of the 4 Marcoss here. It leaves better than it pulls: 105.1 mph at the lights is only the 1,324th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 7 of 7 published acceleration figures for this car.
| Specification | Marcos LM500 |
|---|---|
| Year | 2015 |
| Power | 321 bhp |
| Kerb mass | 1,103 kg |
| Power to weight | 291 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Naturally aspirated |
| Top speed | 268 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Shelby Cobra 260 S/C CSX2000 | 1962 | 4.23 s | 12.78 s | 109.1 mph | 260 bhp |
| Honda NSX-R facelift | 2002 | 4.13 s | 12.78 s | 111.3 mph | 290 bhp |
| Shelby Series 1 | 1998 | 4.00 s | 12.67 s | 111.0 mph | 321 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.