← My Auto Racer All cars Infiniti 0-60 Comparisons Answers

Infiniti QX50 3.7 V6 325

The Infiniti QX50 3.7 V6 325 reaches 60 mph in 6.01 s (100 km/h in 6.37 s) and covers a standing quarter mile in 14.57 s, tripping the lights at 93.4 mph. It clears the first 60 ft in 2.15 s and the eighth mile in 9.30 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.

Infiniti QX50 3.7 V6 325 Cadillac CTS 3.6 V6

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Infiniti QX50 3.7 V6 325
0–60 mph6.01 s
0–100 km/h6.37 s
0–100 mph—
60 ft2.15 s
1/8 mile9.30 s
1/4 mile14.57 s
Trap speed93.4 mph

About the QX50 3.7 V6 325

The 2016 Infiniti QX50 3.7 V6 325 is an all-wheel-drive naturally aspirated saloon of 1,823 kg with 325 bhp, which works out at 178 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.15 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 3,267th quickest to 60 mph, inside the fastest quarter, and the 28th quickest of the 56 Infinitis here. Its 93.4 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 2 of 2 published acceleration figures for this car.

On paper

Specification Infiniti QX50 3.7 V6 325
Year2016
Power325 hp (242 kW)
Kerb mass1,823 kg
Power to weight178 bhp/t
DrivetrainAll-wheel drive
Gears7
EngineNaturally aspirated
Top speed140 mph (225 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Cadillac CTS 3.6 V620086.03 s14.51 s97.9 mph307 bhp
Maserati Quattroporte IV19945.94 s14.47 s98.1 mph284 bhp
Lexus LS 600H L20136.03 s14.42 s101.0 mph439 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.

Where these times sit

0-60 under 7 seconds4,651 cars0-100 km/h under 7 seconds4,031 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Infiniti 0-60 timesevery modelFastest 4x4s and all-wheel-drive cars2,981 carsFastest cars of the 2010s4,541 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Infiniti QX50 3.7 V6 325 0-60 time?
The Infiniti QX50 3.7 V6 325 reaches 60 mph in 6.01 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,267th quickest of the 14,946 cars in the set.
What is the Infiniti QX50 3.7 V6 325 quarter mile time?
14.57 s at 93.4 mph. It reaches the eighth mile in 9.30 s and clears the first 60 ft in 2.15 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Infiniti QX50 3.7 V6 325 have?
325 bhp and 1,823 kg, which is 178 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 7 gears and a quoted top speed of 225 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Infiniti QX50 3.7 V6 325?
Closest here on pace: Cadillac CTS 3.6 V6 (6.03 s), Maserati Quattroporte IV (5.94 s), Lexus LS 600H L (6.03 s). Each one can be raced against the Infiniti QX50 3.7 V6 325 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Infiniti QX50 3.7 V6 325 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.