← My Auto Racer All cars Artega 0-60 Comparisons
The Artega GT reaches 60 mph in 4.03 s and covers a standing quarter mile in 12.72 s, tripping the lights at 110.6 mph. It clears the first 60 ft in 1.95 s and the eighth mile in 8.21 s, reaching 100 mph in 10.41 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 | Artega GT |
|---|---|
| 0–60 mph | 4.03 s |
| 0–100 mph | 10.41 s |
| 60 ft | 1.95 s |
| 1/8 mile | 8.21 s |
| 1/4 mile | 12.72 s |
| Trap speed | 110.6 mph |
The 2009 Artega GT is a rear-drive naturally aspirated supercar of 1,272 kg with 295 bhp, which works out at 232 bhp per tonne. Rear drive and 232 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.95 s. Against the 2,929 cars in the set it is the 809th quickest to 60 mph. It leaves better than it pulls: 110.6 mph at the lights is only the 994th 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 | Artega GT |
|---|---|
| Year | 2009 |
| Power | 295 bhp |
| Kerb mass | 1,272 kg |
| Power to weight | 232 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 273 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Xpeng G6 AWD Performance | 2023 | 4.04 s | 12.63 s | 109.7 mph | 469 bhp |
| Polestar 2 Performance Edition | 2023 | 4.03 s | 12.63 s | 109.3 mph | 469 bhp |
| Ford Mustang SVT Cobra R Mk IV 390 PS | 2000 | 4.13 s | 12.75 s | 111.8 mph | 385 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.