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

Nissan X-Trail 2.5 16V 165

The Nissan X-Trail 2.5 16V 165 reaches 60 mph in 9.02 s (100 km/h in 9.53 s) and covers a standing quarter mile in 16.90 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.83 s and the eighth mile in 10.97 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 X-Trail 2.5 16V 165 Subaru Forester 2.5 152

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 X-Trail 2.5 16V 165
0–60 mph9.02 s
0–100 km/h9.53 s
0–100 mph—
60 ft2.83 s
1/8 mile10.97 s
1/4 mile16.90 s
Trap speed83.2 mph

About the X-Trail 2.5 16V 165

The 2001 Nissan X-Trail 2.5 16V 165 is an all-wheel-drive naturally aspirated SUV of 1,410 kg with 162 bhp, which works out at 115 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.83 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 8,437th quickest to 60 mph, and the 89th quickest of the 263 Nissans here. Its 83.2 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 X-Trail 2.5 16V 165
Year2001
Power162 hp (121 kW)
Kerb mass1,410 kg
Power to weight115 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Subaru Forester 2.5 15220029.02 s16.90 s83.2 mph150 bhp
Renault Kadjar 160 TCe GBF 16020188.95 s16.89 s83.0 mph158 bhp
MG GS 1.5 TGI 16620159.03 s16.75 s82.7 mph164 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
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 X-Trail 2.5 16V 165 0-60 time?
The Nissan X-Trail 2.5 16V 165 reaches 60 mph in 9.02 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,437th quickest of the 14,946 cars in the set.
What is the Nissan X-Trail 2.5 16V 165 quarter mile time?
16.90 s at 83.2 mph. It reaches the eighth mile in 10.97 s and clears the first 60 ft in 2.83 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Nissan X-Trail 2.5 16V 165 have?
162 bhp and 1,410 kg, which is 115 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 5 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Nissan X-Trail 2.5 16V 165?
Closest here on pace: Subaru Forester 2.5 152 (9.02 s), Renault Kadjar 160 TCe GBF 160 (8.95 s), MG GS 1.5 TGI 166 (9.03 s). Each one can be raced against the Nissan X-Trail 2.5 16V 165 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 X-Trail 2.5 16V 165 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.