← My Auto Racer All cars Ariel 0-60 Comparisons
The Ariel Atom 500 V8 reaches 60 mph in 2.00 s and covers a standing quarter mile in 9.68 s, tripping the lights at 142.0 mph. It clears the first 60 ft in 1.40 s and the eighth mile in 6.26 s, reaching 100 mph in 4.79 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 | Ariel Atom 500 V8 |
|---|---|
| 0–60 mph | 2.00 s |
| 0–100 mph | 4.79 s |
| 60 ft | 1.40 s |
| 1/8 mile | 6.26 s |
| 1/4 mile | 9.68 s |
| Trap speed | 142.0 mph |
The 2010 Ariel Atom 500 V8 is a rear-drive naturally aspirated car of 550 kg with 475 bhp, which works out at 863 bhp per tonne. Rear drive and 863 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.40 s. Against the 2,929 cars in the set it is the 14th quickest to 60 mph, inside the fastest one per cent of the set, and the quickest of the 4 Ariels here. Its 142.0 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 5 of 5 published acceleration figures for this car.
| Specification | Ariel Atom 500 V8 |
|---|---|
| Year | 2010 |
| Power | 475 bhp |
| Kerb mass | 550 kg |
| Power to weight | 863 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 275 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Donkervoort F22 | 2023 | 2.17 s | 9.70 s | 140.7 mph | 492 bhp |
| Ariel Atom 4R | 2023 | 2.22 s | 9.83 s | 139.9 mph | 400 bhp |
| Bugatti Centodieci | 2019 | 2.08 s | 9.17 s | 155.7 mph | 1,578 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.