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

Ssangyong Tivoli XLV 1.6 115

The Ssangyong Tivoli XLV 1.6 115 reaches 60 mph in 10.77 s (100 km/h in 11.55 s) and covers a standing quarter mile in 17.87 s, tripping the lights at 75.2 mph. It clears the first 60 ft in 2.60 s and the eighth mile in 11.34 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.

Ssangyong Tivoli XLV 1.6 115 Skoda Yeti 1.2 TSI 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 Ssangyong Tivoli XLV 1.6 115
0–60 mph10.77 s
0–100 km/h11.55 s
0–100 mph—
60 ft2.60 s
1/8 mile11.34 s
1/4 mile17.87 s
Trap speed75.2 mph

About the Tivoli XLV 1.6 115

The 2016 Ssangyong Tivoli XLV 1.6 115 is an all-wheel-drive turbodiesel SUV of 1,535 kg with 114 bhp, which works out at 74 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.60 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 11,329th quickest to 60 mph, and the 7th quickest of the 20 Ssangyongs here. It leaves better than it pulls: 75.2 mph at the lights is only the 12,508th 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 Ssangyong Tivoli XLV 1.6 115
Year2016
Power114 hp (85 kW)
Kerb mass1,535 kg
Power to weight74 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed107 mph (172 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Yeti 1.2 TSI 105201310.70 s17.87 s76.6 mph103 bhp
Nissan Qashqai 1.5 dCI 110201810.81 s17.87 s76.5 mph109 bhp
Nissan Qashqai 1.5 dCi 110 (J11)201410.81 s17.89 s76.7 mph109 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
Ssangyong 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 Ssangyong Tivoli XLV 1.6 115 0-60 time?
The Ssangyong Tivoli XLV 1.6 115 reaches 60 mph in 10.77 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,329th quickest of the 14,946 cars in the set.
What is the Ssangyong Tivoli XLV 1.6 115 quarter mile time?
17.87 s at 75.2 mph. It reaches the eighth mile in 11.34 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 Ssangyong Tivoli XLV 1.6 115 have?
114 bhp and 1,535 kg, which is 74 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 172 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ssangyong Tivoli XLV 1.6 115?
Closest here on pace: Skoda Yeti 1.2 TSI 105 (10.70 s), Nissan Qashqai 1.5 dCI 110 (10.81 s), Nissan Qashqai 1.5 dCi 110 (J11) (10.81 s). Each one can be raced against the Ssangyong Tivoli XLV 1.6 115 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 Ssangyong Tivoli XLV 1.6 115 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.