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

Nissan Qashqai 2.0 CVT 141

The Nissan Qashqai 2.0 CVT 141 reaches 60 mph in 10.16 s (100 km/h in 10.89 s) and covers a standing quarter mile in 17.67 s, tripping the lights at 77.5 mph. It clears the first 60 ft in 2.77 s and the eighth mile in 11.32 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 Qashqai 2.0 CVT 141 Chrysler PT Cruiser 2.2 CRD 150

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 Qashqai 2.0 CVT 141
0–60 mph10.16 s
0–100 km/h10.89 s
0–100 mph—
60 ft2.77 s
1/8 mile11.32 s
1/4 mile17.67 s
Trap speed77.5 mph

About the Qashqai 2.0 CVT 141

The 2010 Nissan Qashqai 2.0 CVT 141 is an all-wheel-drive naturally aspirated SUV of 1,378 kg with 139 bhp, which works out at 101 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.77 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 10,413th quickest to 60 mph, and the 128th quickest of the 263 Nissans here. It leaves better than it pulls: 77.5 mph at the lights is only the 11,385th 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 Nissan Qashqai 2.0 CVT 141
Year2010
Power139 hp (104 kW)
Kerb mass1,378 kg
Power to weight101 bhp/t
DrivetrainAll-wheel drive
Gears1
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chrysler PT Cruiser 2.2 CRD 150200610.15 s17.59 s78.2 mph148 bhp
Proton Exora 1.6 CVT 140201210.17 s17.67 s77.8 mph138 bhp
Toyota Land Cruiser 100 4.7 V8 32V 238200210.16 s17.79 s79.3 mph235 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 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 Nissan Qashqai 2.0 CVT 141 0-60 time?
The Nissan Qashqai 2.0 CVT 141 reaches 60 mph in 10.16 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,413th quickest of the 14,946 cars in the set.
What is the Nissan Qashqai 2.0 CVT 141 quarter mile time?
17.67 s at 77.5 mph. It reaches the eighth mile in 11.32 s and clears the first 60 ft in 2.77 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Nissan Qashqai 2.0 CVT 141 have?
139 bhp and 1,378 kg, which is 101 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 1 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Nissan Qashqai 2.0 CVT 141?
Closest here on pace: Chrysler PT Cruiser 2.2 CRD 150 (10.15 s), Proton Exora 1.6 CVT 140 (10.17 s), Toyota Land Cruiser 100 4.7 V8 32V 238 (10.16 s). Each one can be raced against the Nissan Qashqai 2.0 CVT 141 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 Qashqai 2.0 CVT 141 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.