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

Renault Kadjar 160 TCe GBF 160

The Renault Kadjar 160 TCe GBF 160 reaches 60 mph in 8.95 s (100 km/h in 9.51 s) and covers a standing quarter mile in 16.89 s, tripping the lights at 83.0 mph. It clears the first 60 ft in 2.60 s and the eighth mile in 10.89 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.

Renault Kadjar 160 TCe GBF 160 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 Renault Kadjar 160 TCe GBF 160
0–60 mph8.95 s
0–100 km/h9.51 s
0–100 mph—
60 ft2.60 s
1/8 mile10.89 s
1/4 mile16.89 s
Trap speed83.0 mph

About the Kadjar 160 TCe GBF 160

The 2018 Renault Kadjar 160 TCe GBF 160 is a front-drive turbocharged SUV of 1,442 kg with 158 bhp, which works out at 110 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.60 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,347th quickest to 60 mph, and the 123rd quickest of the 499 Renaults here. Its 83.0 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 Renault Kadjar 160 TCe GBF 160
Year2018
Power158 hp (118 kW)
Kerb mass1,442 kg
Power to weight110 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Subaru Forester 2.5 15220029.02 s16.90 s83.2 mph150 bhp
Subaru Outback 2.5i CVT 17520148.89 s16.85 s81.4 mph173 bhp
Subaru Outback 2.5 16520058.93 s16.80 s84.1 mph162 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
Renault 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 Renault Kadjar 160 TCe GBF 160 0-60 time?
The Renault Kadjar 160 TCe GBF 160 reaches 60 mph in 8.95 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,347th quickest of the 14,946 cars in the set.
What is the Renault Kadjar 160 TCe GBF 160 quarter mile time?
16.89 s at 83.0 mph. It reaches the eighth mile in 10.89 s and clears the first 60 ft in 2.60 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Renault Kadjar 160 TCe GBF 160 have?
158 bhp and 1,442 kg, which is 110 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Renault Kadjar 160 TCe GBF 160?
Closest here on pace: Subaru Forester 2.5 152 (9.02 s), Subaru Outback 2.5i CVT 175 (8.89 s), Subaru Outback 2.5 165 (8.93 s). Each one can be raced against the Renault Kadjar 160 TCe GBF 160 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 Renault Kadjar 160 TCe GBF 160 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.