Skip, RouteMap's route guideRouteplanner.app
Routeplanner.app

RenčeDekani

Distance: 50 mi·Duration: 1 h 5 min

Save for offline?

We'll download this route and its map area so it works without a connection. This can take a moment -- you can keep using the app while it finishes.

Driving from Renče to Dekani takes about via H4. The distance is 50 mi. The straight-line distance is 25 mi. EV charging is available along the route, including in Gradišče nad Prvačino, Križ, Senožeče, Sežana, Spodnje Škofije. Driving directions

Driving directions

23 · 50 mi
  1. 1 Depart 7 yd
  2. 2 Turn sharp right onto Trg 20 yd
  3. 3 Turn left onto Trg 1 mi
  4. 4 Enter roundabout right 16 yd
  5. 5 Exit roundabout right 1 mi
  6. 6 At end of road, turn right 1 mi
  7. 7 At end of road, turn right 1 mi
  8. 8 Turn left 3 mi
  9. 9 Take ramp right 1 mi
  10. 10 Keep slightly right 1 mi
  11. 11 Merge slightly left 22 mi
  12. 12 Keep slightly right 1 mi
  13. 13 Merge slightly left 20 mi
  1. 14 Take exit slightly right 1 mi
  2. 15 Turn right 1 mi
  3. 16 Turn left 1 mi
  4. 17 Continue straight onto Rižana 1 mi
  5. 18 Turn straight 3 mi
  6. 19 Continue right onto Dekani 1 mi
  7. 20 Continue right onto Dekani 1 mi
  8. 21 Continue left onto Dekani 79 yd
  9. 22 Continue slightly left onto Dekani 32 yd
  10. 23 Arrive onto Dekani

The return trip from Dekani to Renče covers roughly the same distance, 50 mi.

Questions and answers

Dekani lies roughly to the south of Renče.

How far is it from Renče to Dekani?

The distance between Renče and Dekani is 50 mi by road.

How long does it take to drive from Renče to Dekani?

The drive from Renče to Dekani takes approximately 1 h 5 min by car.

What is the best route from Renče to Dekani?

The fastest route from Renče to Dekani covers 50 mi with a driving time of approximately 1 h 5 min.

What is the shortest route from Renče to Dekani?

The shortest driving route from Renče to Dekani is about 50 mi by road.

Sources

Distance and drive time are computed from OpenStreetMap road data with the OSRM routing engine. Updated .