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

Infiniti QX4 3.5 V6 243

The Infiniti QX4 3.5 V6 243 reaches 60 mph in 8.18 s (100 km/h in 8.72 s) and covers a standing quarter mile in 16.53 s, tripping the lights at 83.6 mph. It clears the first 60 ft in 2.74 s and the eighth mile in 10.64 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 QX4 3.5 V6 243 Renault Avantime 3.0 V6 210

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 QX4 3.5 V6 243
0–60 mph8.18 s
0–100 km/h8.72 s
0–100 mph—
60 ft2.74 s
1/8 mile10.64 s
1/4 mile16.53 s
Trap speed83.6 mph

About the QX4 3.5 V6 243

The 2001 Infiniti QX4 3.5 V6 243 is an all-wheel-drive turbocharged SUV of 1,974 kg with 240 bhp, which works out at 122 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.74 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 6,865th quickest to 60 mph, and the 51st quickest of the 56 Infinitis here. It leaves better than it pulls: 83.6 mph at the lights is only the 8,059th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Infiniti QX4 3.5 V6 243
Year2001
Power240 hp (179 kW)
Kerb mass1,974 kg
Power to weight122 bhp/t
DrivetrainAll-wheel drive
Gears4
EngineTurbocharged
Top speed110 mph (177 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Avantime 3.0 V6 21020018.16 s16.49 s87.5 mph204 bhp
Renault Arkana 1.3 MHEV 160 EDC 15820248.19 s16.43 s83.1 mph156 bhp
Nissan Quest 3.5 V6 23520098.15 s16.40 s85.4 mph232 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 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 SUVs2,049 carsFastest cars of the 2000s5,138 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 QX4 3.5 V6 243 0-60 time?
The Infiniti QX4 3.5 V6 243 reaches 60 mph in 8.18 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,865th quickest of the 14,946 cars in the set.
What is the Infiniti QX4 3.5 V6 243 quarter mile time?
16.53 s at 83.6 mph. It reaches the eighth mile in 10.64 s and clears the first 60 ft in 2.74 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Infiniti QX4 3.5 V6 243 have?
240 bhp and 1,974 kg, which is 122 bhp per tonne. It is all-wheel-drive, turbocharged, with 4 gears and a quoted top speed of 177 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Infiniti QX4 3.5 V6 243?
Closest here on pace: Renault Avantime 3.0 V6 210 (8.16 s), Renault Arkana 1.3 MHEV 160 EDC 158 (8.19 s), Nissan Quest 3.5 V6 235 (8.15 s). Each one can be raced against the Infiniti QX4 3.5 V6 243 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 QX4 3.5 V6 243 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.