Loen

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:47:21Z.

Havn

havn_id:
2328150
navn:
Loen
kode:
NOLOE
type:
Havn
kommune:
Stryn
fylke:
Vestland
lat:
61.87246
lon:
6.84192

Port-call and departure connections

39 results

  1. oid:
    2328150
    origin:
    Loen
    did:
    2328133
    destination:
    Selje
  2. oid:
    2328150
    origin:
    Loen
    did:
    2328173
    destination:
    Geiranger
  3. oid:
    2328150
    origin:
    Loen
    did:
    2328100
    destination:
    Måløy
  4. oid:
    2328150
    origin:
    Loen
    did:
    2328100
    destination:
    Måløy
  5. oid:
    2328150
    origin:
    Loen
    did:
    2451774
    destination:
    Kalvneset
  6. oid:
    2465373
    origin:
    Davika ankring
    did:
    2328150
    destination:
    Loen
  7. oid:
    2467326
    origin:
    Sandane ankring
    did:
    2328150
    destination:
    Loen
  8. oid:
    2328117
    origin:
    Vik - Sogn
    did:
    2328150
    destination:
    Loen
  9. oid:
    2328117
    origin:
    Vik - Sogn
    did:
    2328150
    destination:
    Loen
  10. oid:
    2468668
    origin:
    Fresvik ankring
    did:
    2328150
    destination:
    Loen
  11. oid:
    2328048
    origin:
    Stavanger
    did:
    2328150
    destination:
    Loen
  12. oid:
    2328107
    origin:
    Sandane
    did:
    2328150
    destination:
    Loen
  13. oid:
    2328107
    origin:
    Sandane
    did:
    2328150
    destination:
    Loen
  14. oid:
    2328232
    origin:
    Ålesund
    did:
    2328150
    destination:
    Loen
  15. oid:
    2328232
    origin:
    Ålesund
    did:
    2328150
    destination:
    Loen
  16. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2328150
    destination:
    Loen
  17. oid:
    2328078
    origin:
    Bergen
    did:
    2328150
    destination:
    Loen
  18. oid:
    2328078
    origin:
    Bergen
    did:
    2328150
    destination:
    Loen
  19. oid:
    2328078
    origin:
    Bergen
    did:
    2328150
    destination:
    Loen
  20. oid:
    2328078
    origin:
    Bergen
    did:
    2328150
    destination:
    Loen
  21. oid:
    2328148
    origin:
    Kalvåg
    did:
    2328150
    destination:
    Loen
  22. oid:
    2328148
    origin:
    Kalvåg
    did:
    2328150
    destination:
    Loen
  23. oid:
    2328148
    origin:
    Kalvåg
    did:
    2328150
    destination:
    Loen
  24. oid:
    2328100
    origin:
    Måløy
    did:
    2328150
    destination:
    Loen
  25. oid:
    2328100
    origin:
    Måløy
    did:
    2328150
    destination:
    Loen
  26. oid:
    2328100
    origin:
    Måløy
    did:
    2328150
    destination:
    Loen
  27. oid:
    2328077
    origin:
    Balestrand
    did:
    2328150
    destination:
    Loen
  28. oid:
    2328150
    origin:
    Loen
    did:
    2457196
    destination:
    Øye
  29. oid:
    2328150
    origin:
    Loen
    did:
    2457196
    destination:
    Øye
  30. oid:
    2328150
    origin:
    Loen
    did:
    2457196
    destination:
    Øye
  31. oid:
    2328150
    origin:
    Loen
    did:
    2457196
    destination:
    Øye
  32. oid:
    2328150
    origin:
    Loen
    did:
    2328232
    destination:
    Ålesund
  33. oid:
    2328150
    origin:
    Loen
    did:
    2328232
    destination:
    Ålesund
  34. oid:
    2328150
    origin:
    Loen
    did:
    2328232
    destination:
    Ålesund
  35. oid:
    2328150
    origin:
    Loen
    did:
    2328179
    destination:
    Hellesylt
  36. oid:
    2328150
    origin:
    Loen
    did:
    2328179
    destination:
    Hellesylt
  37. oid:
    2328150
    origin:
    Loen
    did:
    2465713
    destination:
    Finnafjorden ankring
  38. oid:
    2328150
    origin:
    Loen
    did:
    2328117
    destination:
    Vik - Sogn
  39. oid:
    2328150
    origin:
    Loen
    did:
    2467326
    destination:
    Sandane ankring

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.