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

Nissan Pathfinder 2.5 dCi 171

The Nissan Pathfinder 2.5 dCi 171 reaches 60 mph in 10.62 s (100 km/h in 11.36 s) and covers a standing quarter mile in 17.94 s, tripping the lights at 76.5 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 11.50 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.

Nissan Pathfinder 2.5 dCi 171 Dodge Journey 2.0 CRD 140

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 Nissan Pathfinder 2.5 dCi 171
0–60 mph10.62 s
0–100 km/h11.36 s
0–100 mph—
60 ft2.86 s
1/8 mile11.50 s
1/4 mile17.94 s
Trap speed76.5 mph

About the Pathfinder 2.5 dCi 171

The 2007 Nissan Pathfinder 2.5 dCi 171 is an all-wheel-drive turbodiesel SUV of 2,081 kg with 169 bhp, which works out at 81 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.86 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 11,146th quickest to 60 mph, and the 142nd quickest of the 263 Nissans here. Its 76.5 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 Nissan Pathfinder 2.5 dCi 171
Year2007
Power169 hp (126 kW)
Kerb mass2,081 kg
Power to weight81 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineTurbodiesel
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Journey 2.0 CRD 140200810.64 s17.83 s76.5 mph138 bhp
Dacia Duster 1.5 dCi 110 (2017)201710.70 s17.91 s75.8 mph109 bhp
Opel Crossland X 1.2 110201710.65 s17.81 s76.6 mph109 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Nissan 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 Nissan Pathfinder 2.5 dCi 171 0-60 time?
The Nissan Pathfinder 2.5 dCi 171 reaches 60 mph in 10.62 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,146th quickest of the 14,946 cars in the set.
What is the Nissan Pathfinder 2.5 dCi 171 quarter mile time?
17.94 s at 76.5 mph. It reaches the eighth mile in 11.50 s and clears the first 60 ft in 2.86 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Nissan Pathfinder 2.5 dCi 171 have?
169 bhp and 2,081 kg, which is 81 bhp per tonne. It is all-wheel-drive, turbodiesel, with 5 gears and a quoted top speed of 175 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Nissan Pathfinder 2.5 dCi 171?
Closest here on pace: Dodge Journey 2.0 CRD 140 (10.64 s), Dacia Duster 1.5 dCi 110 (2017) (10.70 s), Opel Crossland X 1.2 110 (10.65 s). Each one can be raced against the Nissan Pathfinder 2.5 dCi 171 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 Nissan Pathfinder 2.5 dCi 171 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.