Sjøholt

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T16:18:01Z.

Havn

havn_id:
2328211
navn:
Sjøholt
kode:
NOSJO
type:
Havn
kommune:
Ålesund
fylke:
Møre og Romsdal
lat:
62.48159
lon:
6.80423

Port-call and departure connections

36 results

  1. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328230
    destination:
    Ørsta
  2. oid:
    2328212
    origin:
    Skogn
    did:
    2328211
    destination:
    Sjøholt
  3. oid:
    2328211
    origin:
    Sjøholt
    did:
    2450397
    destination:
    Bjordal
  4. oid:
    2452175
    origin:
    Valldal
    did:
    2328211
    destination:
    Sjøholt
  5. oid:
    2328211
    origin:
    Sjøholt
    did:
    2447404
    destination:
    Storesund
  6. oid:
    2456951
    origin:
    Malo
    did:
    2328211
    destination:
    Sjøholt
  7. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328224
    destination:
    Ulsteinvik
  8. oid:
    2328224
    origin:
    Ulsteinvik
    did:
    2328211
    destination:
    Sjøholt
  9. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328107
    destination:
    Sandane
  10. oid:
    2452175
    origin:
    Valldal
    did:
    2328211
    destination:
    Sjøholt
  11. oid:
    2328211
    origin:
    Sjøholt
    did:
    2447404
    destination:
    Storesund
  12. oid:
    2456951
    origin:
    Malo
    did:
    2328211
    destination:
    Sjøholt
  13. oid:
    2328211
    origin:
    Sjøholt
    did:
    2447769
    destination:
    Mjølstadneset
  14. oid:
    2447769
    origin:
    Mjølstadneset
    did:
    2328211
    destination:
    Sjøholt
  15. oid:
    2328211
    origin:
    Sjøholt
    did:
    2456951
    destination:
    Malo
  16. oid:
    2328151
    origin:
    Vågsfjorden
    did:
    2328211
    destination:
    Sjøholt
  17. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  18. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  19. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  20. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  21. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  22. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  23. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  24. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  25. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  26. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  27. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  28. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  29. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  30. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  31. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  32. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  33. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  34. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt
  35. oid:
    2328211
    origin:
    Sjøholt
    did:
    2328232
    destination:
    Ålesund
  36. oid:
    2328232
    origin:
    Ålesund
    did:
    2328211
    destination:
    Sjøholt

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.