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

Nissan Cube 1.5 CVT 116

The Nissan Cube 1.5 CVT 116 reaches 60 mph in 8.96 s (100 km/h in 9.62 s) and covers a standing quarter mile in 16.94 s, tripping the lights at 79.4 mph. It clears the first 60 ft in 2.59 s and the eighth mile in 10.78 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 Cube 1.5 CVT 116 Renault Kadjar 140 TCe GPF 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 Cube 1.5 CVT 116
0–60 mph8.96 s
0–100 km/h9.62 s
0–100 mph—
60 ft2.59 s
1/8 mile10.78 s
1/4 mile16.94 s
Trap speed79.4 mph

About the Cube 1.5 CVT 116

The 2009 Nissan Cube 1.5 CVT 116 is a front-drive naturally aspirated SUV of 1,200 kg with 114 bhp, which works out at 95 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.59 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 8,361st quickest to 60 mph, and the 87th quickest of the 263 Nissans here. It leaves better than it pulls: 79.4 mph at the lights is only the 10,313th 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 Cube 1.5 CVT 116
Year2009
Power114 hp (85 kW)
Kerb mass1,200 kg
Power to weight95 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed106 mph (171 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Kadjar 140 TCe GPF 14020188.94 s16.91 s82.3 mph138 bhp
Lancia Musa 1.6 Multijet 12020038.99 s16.82 s82.1 mph118 bhp
Mitsubishi Outlander 2.2 MIVEC 2WD 15020128.87 s16.88 s81.6 mph148 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 Cube 1.5 CVT 116 0-60 time?
The Nissan Cube 1.5 CVT 116 reaches 60 mph in 8.96 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,361st quickest of the 14,946 cars in the set.
What is the Nissan Cube 1.5 CVT 116 quarter mile time?
16.94 s at 79.4 mph. It reaches the eighth mile in 10.78 s and clears the first 60 ft in 2.59 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Nissan Cube 1.5 CVT 116 have?
114 bhp and 1,200 kg, which is 95 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 171 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Nissan Cube 1.5 CVT 116?
Closest here on pace: Renault Kadjar 140 TCe GPF 140 (8.94 s), Lancia Musa 1.6 Multijet 120 (8.99 s), Mitsubishi Outlander 2.2 MIVEC 2WD 150 (8.87 s). Each one can be raced against the Nissan Cube 1.5 CVT 116 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 Cube 1.5 CVT 116 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.