← My Auto Racer All cars Infiniti 0-60 Comparisons
The Infiniti G37 Sedan reaches 60 mph in 5.32 s and covers a standing quarter mile in 13.75 s, tripping the lights at 103.9 mph. It clears the first 60 ft in 2.30 s and the eighth mile in 9.00 s, reaching 100 mph in 12.47 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 | Infiniti G37 Sedan |
|---|---|
| 0–60 mph | 5.32 s |
| 0–100 mph | 12.47 s |
| 60 ft | 2.30 s |
| 1/8 mile | 9.00 s |
| 1/4 mile | 13.75 s |
| Trap speed | 103.9 mph |
The 2009 Infiniti G37 Sedan is a rear-drive naturally aspirated saloon of 1,709 kg with 315 bhp, which works out at 184 bhp per tonne. Rear drive and 184 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.30 s. Against the 2,929 cars in the set it is the 1,578th quickest to 60 mph, and the 7th quickest of the 18 Infinitis here. Its 103.9 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 | Infiniti G37 Sedan |
|---|---|
| Year | 2009 |
| Power | 315 bhp |
| Kerb mass | 1,709 kg |
| Power to weight | 184 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 250 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Jaguar F-Pace 3.0 S | 2016 | 5.33 s | 13.90 s | 100.3 mph | 374 bhp |
| Vauxhall VXR8 | 2007 | 5.39 s | 13.71 s | 102.8 mph | 412 bhp |
| Hyundai Genesis 4.6 | 2009 | 5.11 s | 13.66 s | 102.6 mph | 375 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.