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

Jeep Renegade 1.6 e-Torque 110

The Jeep Renegade 1.6 e-Torque 110 reaches 60 mph in 10.75 s (100 km/h in 11.39 s) and covers a standing quarter mile in 18.10 s, tripping the lights at 77.9 mph. It clears the first 60 ft in 3.07 s and the eighth mile in 11.77 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.

Jeep Renegade 1.6 e-Torque 110 Dacia Logan MCV 1.6 16v 105

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 Jeep Renegade 1.6 e-Torque 110
0–60 mph10.75 s
0–100 km/h11.39 s
0–100 mph—
60 ft3.07 s
1/8 mile11.77 s
1/4 mile18.10 s
Trap speed77.9 mph

About the Renegade 1.6 e-Torque 110

The 2014 Jeep Renegade 1.6 e-Torque 110 is a front-drive naturally aspirated SUV of 1,346 kg with 109 bhp, which works out at 81 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.07 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 11,304th quickest to 60 mph, and the 60th quickest of the 68 Jeeps here. Its 77.9 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 Jeep Renegade 1.6 e-Torque 110
Year2014
Power109 hp (81 kW)
Kerb mass1,346 kg
Power to weight81 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed111 mph (179 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dacia Logan MCV 1.6 16v 105200810.74 s18.12 s77.5 mph103 bhp
Vauxhall Mokka X 1.6i ecoTEC 115201610.73 s18.13 s77.2 mph114 bhp
Daewoo Tacuma/Rezzo 1.6 105200010.72 s18.14 s76.8 mph103 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
Jeep 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 Jeep Renegade 1.6 e-Torque 110 0-60 time?
The Jeep Renegade 1.6 e-Torque 110 reaches 60 mph in 10.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,304th quickest of the 14,946 cars in the set.
What is the Jeep Renegade 1.6 e-Torque 110 quarter mile time?
18.10 s at 77.9 mph. It reaches the eighth mile in 11.77 s and clears the first 60 ft in 3.07 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jeep Renegade 1.6 e-Torque 110 have?
109 bhp and 1,346 kg, which is 81 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 179 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jeep Renegade 1.6 e-Torque 110?
Closest here on pace: Dacia Logan MCV 1.6 16v 105 (10.74 s), Vauxhall Mokka X 1.6i ecoTEC 115 (10.73 s), Daewoo Tacuma/Rezzo 1.6 105 (10.72 s). Each one can be raced against the Jeep Renegade 1.6 e-Torque 110 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 Jeep Renegade 1.6 e-Torque 110 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.