Leikanger

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T07:38:16Z.

Havn

havn_id:
2467242
navn:
Leikanger
kode:
NOSOG
type:
Havn
kommune:
Sogndal
fylke:
Vestland
lat:
61.18276
lon:
6.79749

Port-call and departure connections

53 results

  1. oid:
    2467242
    origin:
    Leikanger
    did:
    2447386
    destination:
    Visnes - Eide
  2. oid:
    2467242
    origin:
    Leikanger
    did:
    2465372
    destination:
    Ålfoten
  3. oid:
    2458171
    origin:
    Seljestokken
    did:
    2467242
    destination:
    Leikanger
  4. oid:
    2467242
    origin:
    Leikanger
    did:
    2447376
    destination:
    Leirvik i Hyllestad
  5. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2467242
    destination:
    Leikanger
  6. oid:
    2467242
    origin:
    Leikanger
    did:
    2328084
    destination:
    Florø
  7. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2467242
    destination:
    Leikanger
  8. oid:
    2467242
    origin:
    Leikanger
    did:
    2328119
    destination:
    Årdalstangen
  9. oid:
    2328084
    origin:
    Florø
    did:
    2467242
    destination:
    Leikanger
  10. oid:
    2467242
    origin:
    Leikanger
    did:
    2328084
    destination:
    Florø
  11. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2467242
    destination:
    Leikanger
  12. oid:
    2467242
    origin:
    Leikanger
    did:
    2447404
    destination:
    Storesund
  13. oid:
    2341629
    origin:
    Stryn
    did:
    2467242
    destination:
    Leikanger
  14. oid:
    2467242
    origin:
    Leikanger
    did:
    2447404
    destination:
    Storesund
  15. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  16. oid:
    2467242
    origin:
    Leikanger
    did:
    2328086
    destination:
    Fusa
  17. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  18. oid:
    2467242
    origin:
    Leikanger
    did:
    2328975
    destination:
    Wismar
  19. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  20. oid:
    2467242
    origin:
    Leikanger
    did:
    2328094
    destination:
    Kaupanger
  21. oid:
    2450231
    origin:
    Eikelandsosen
    did:
    2467242
    destination:
    Leikanger
  22. oid:
    2467242
    origin:
    Leikanger
    did:
    2328094
    destination:
    Kaupanger
  23. oid:
    2327996
    origin:
    Kvinesdal
    did:
    2467242
    destination:
    Leikanger
  24. oid:
    2467242
    origin:
    Leikanger
    did:
    2328084
    destination:
    Florø
  25. oid:
    2450397
    origin:
    Bjordal
    did:
    2467242
    destination:
    Leikanger
  26. oid:
    2467242
    origin:
    Leikanger
    did:
    2341392
    destination:
    Hermansverk
  27. oid:
    2450397
    origin:
    Bjordal
    did:
    2467242
    destination:
    Leikanger
  28. oid:
    2467242
    origin:
    Leikanger
    did:
    2328212
    destination:
    Skogn
  29. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  30. oid:
    2467242
    origin:
    Leikanger
    did:
    2328088
    destination:
    Granvin
  31. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  32. oid:
    2467242
    origin:
    Leikanger
    did:
    2328108
    destination:
    Samnanger
  33. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  34. oid:
    2467242
    origin:
    Leikanger
    did:
    2447404
    destination:
    Storesund
  35. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  36. oid:
    2467242
    origin:
    Leikanger
    did:
    2450381
    destination:
    Skånevikfjorden
  37. oid:
    2327961
    origin:
    Eikefjord
    did:
    2467242
    destination:
    Leikanger
  38. oid:
    2467242
    origin:
    Leikanger
    did:
    2328094
    destination:
    Kaupanger
  39. oid:
    2450231
    origin:
    Eikelandsosen
    did:
    2467242
    destination:
    Leikanger
  40. oid:
    2467242
    origin:
    Leikanger
    did:
    2450230
    destination:
    Eidsnes
  41. oid:
    2328094
    origin:
    Kaupanger
    did:
    2467242
    destination:
    Leikanger
  42. oid:
    2467242
    origin:
    Leikanger
    did:
    2447404
    destination:
    Storesund
  43. oid:
    2328080
    origin:
    Dale
    did:
    2467242
    destination:
    Leikanger
  44. oid:
    2467242
    origin:
    Leikanger
    did:
    2328077
    destination:
    Balestrand
  45. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2467242
    destination:
    Leikanger
  46. oid:
    2467242
    origin:
    Leikanger
    did:
    2328094
    destination:
    Kaupanger
  47. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2467242
    destination:
    Leikanger
  48. oid:
    2467242
    origin:
    Leikanger
    did:
    2328091
    destination:
    Høyanger
  49. oid:
    2328096
    origin:
    Lærdal
    did:
    2467242
    destination:
    Leikanger
  50. oid:
    2467242
    origin:
    Leikanger
    did:
    2447403
    destination:
    Fjærland
  51. oid:
    2458563
    origin:
    Nærøyfjorden
    did:
    2467242
    destination:
    Leikanger
  52. oid:
    2467242
    origin:
    Leikanger
    did:
    2465924
    destination:
    Fanafjorden ankring
  53. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467242
    destination:
    Leikanger

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the port page

Use the port ID and code for identification. Port-call connections describe reported relations in the selected period, not necessarily a current timetable.

Open the port as a place for weather, vessels, charging and geographic context. Use Entur separately if the question concerns onward public transport from the port.