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

LīčiVecate

Distance: 139 km·Drive time: 2 h 10 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 Līči to Vecate takes about via A3. The distance is 139 km. The straight-line distance is 106 km. EV charging is available along the route, including in Baltezers, Skulte, Turaida, Araiši. Driving directions

Driving directions

17 · 139 km
  1. 1 Depart left onto Rīgas iela 2 km
  2. 2 Continue straight onto Rīga - Ērgļi 880 m
  3. 3 Turn sharp left 9 km
  4. 4 Take exit slightly right 792 m
  5. 5 Merge slightly left onto Rīga - Sigulda - Igaunijas robeža (Veclaicene) 23 km
  6. 6 Keep slightly right 66 km
  7. 7 Continue straight 735 m
  8. 8 Take exit slightly right 4 km
  1. 9 Enter roundabout straight onto Valmiera — Matīši — Mazsalaca 255 m
  2. 10 Exit roundabout straight onto Valmiera — Matīši — Mazsalaca 19 km
  3. 11 Continue straight onto Valmieras iela 4 km
  4. 12 Continue straight onto Valmieras iela 639 m
  5. 13 Keep slightly right onto Valmieras iela 60 m
  6. 14 Continue straight onto Mazsalacas iela 2 km
  7. 15 Continue straight onto Valmiera - Matīši - Mazsalaca 10 km
  8. 16 Turn right 210 m
  9. 17 Arrive

The return trip from Vecate to Līči covers roughly the same distance, 139 km.

Questions and answers

Vecate lies roughly to the north-east of Līči.

How far is it from Līči to Vecate?

The distance between Līči and Vecate is 139 km by road.

How long does it take to drive from Līči to Vecate?

The drive from Līči to Vecate takes approximately 2 h 10 min by car.

What is the best route from Līči to Vecate?

The fastest route from Līči to Vecate covers 139 km with a driving time of approximately 2 h 10 min.

What is the shortest route from Līči to Vecate?

The shortest driving route from Līči to Vecate is about 139 km by road.

Sources

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