Allemannsdata
Manual search

Sykkylven

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T13:01:12Z.

Havn

havn_id:
2328220
navn:
Sykkylven
kode:
not reported by source
type:
Havn
kommune:
Sykkylven
fylke:
Møre og Romsdal
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

53 results

  1. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328168
    destination:
    Ellingsøy
  2. oid:
    2447410
    origin:
    Vigra
    did:
    2328220
    destination:
    Sykkylven
  3. oid:
    2328220
    origin:
    Sykkylven
    did:
    2461588
    destination:
    Bjørke
  4. oid:
    2328232
    origin:
    Ålesund
    did:
    2328220
    destination:
    Sykkylven
  5. oid:
    2328220
    origin:
    Sykkylven
    did:
    2452204
    destination:
    Ukjent lokasjon Norge
  6. oid:
    2452223
    origin:
    Alvika
    did:
    2328220
    destination:
    Sykkylven
  7. oid:
    2328220
    origin:
    Sykkylven
    did:
    2452223
    destination:
    Alvika
  8. oid:
    2452223
    origin:
    Alvika
    did:
    2328220
    destination:
    Sykkylven
  9. oid:
    2328220
    origin:
    Sykkylven
    did:
    2452223
    destination:
    Alvika
  10. oid:
    2452223
    origin:
    Alvika
    did:
    2328220
    destination:
    Sykkylven
  11. oid:
    2328220
    origin:
    Sykkylven
    did:
    2452175
    destination:
    Valldal
  12. oid:
    2451938
    origin:
    Skorgeneset
    did:
    2328220
    destination:
    Sykkylven
  13. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328179
    destination:
    Hellesylt
  14. oid:
    2458171
    origin:
    Seljestokken
    did:
    2328220
    destination:
    Sykkylven
  15. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328230
    destination:
    Ørsta
  16. oid:
    2328228
    origin:
    Vestnes
    did:
    2328220
    destination:
    Sykkylven
  17. oid:
    2328220
    origin:
    Sykkylven
    did:
    2456942
    destination:
    Arnvikneset
  18. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  19. oid:
    2328220
    origin:
    Sykkylven
    did:
    2447590
    destination:
    Håeimsvika
  20. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  21. oid:
    2328220
    origin:
    Sykkylven
    did:
    2447590
    destination:
    Håeimsvika
  22. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  23. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328200
    destination:
    Molde
  24. oid:
    2328232
    origin:
    Ålesund
    did:
    2328220
    destination:
    Sykkylven
  25. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328200
    destination:
    Molde
  26. oid:
    2465373
    origin:
    Davika ankring
    did:
    2328220
    destination:
    Sykkylven
  27. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328232
    destination:
    Ålesund
  28. oid:
    2452145
    origin:
    Flem
    did:
    2328220
    destination:
    Sykkylven
  29. oid:
    2328232
    origin:
    Ålesund
    did:
    2328220
    destination:
    Sykkylven
  30. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328230
    destination:
    Ørsta
  31. oid:
    2456951
    origin:
    Malo
    did:
    2328220
    destination:
    Sykkylven
  32. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328230
    destination:
    Ørsta
  33. oid:
    2447590
    origin:
    Håeimsvika
    did:
    2328220
    destination:
    Sykkylven
  34. oid:
    2328220
    origin:
    Sykkylven
    did:
    2447590
    destination:
    Håeimsvika
  35. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  36. oid:
    2328220
    origin:
    Sykkylven
    did:
    2447590
    destination:
    Håeimsvika
  37. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  38. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328230
    destination:
    Ørsta
  39. oid:
    2456951
    origin:
    Malo
    did:
    2328220
    destination:
    Sykkylven
  40. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328230
    destination:
    Ørsta
  41. oid:
    2456951
    origin:
    Malo
    did:
    2328220
    destination:
    Sykkylven
  42. oid:
    2328220
    origin:
    Sykkylven
    did:
    2456951
    destination:
    Malo
  43. oid:
    2327996
    origin:
    Kvinesdal
    did:
    2328220
    destination:
    Sykkylven
  44. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328232
    destination:
    Ålesund
  45. oid:
    2328226
    origin:
    Vartdal
    did:
    2328220
    destination:
    Sykkylven
  46. oid:
    2328220
    origin:
    Sykkylven
    did:
    2456951
    destination:
    Malo
  47. oid:
    2328230
    origin:
    Ørsta
    did:
    2328220
    destination:
    Sykkylven
  48. oid:
    2328220
    origin:
    Sykkylven
    did:
    2447404
    destination:
    Storesund
  49. oid:
    2447590
    origin:
    Håeimsvika
    did:
    2328220
    destination:
    Sykkylven
  50. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328173
    destination:
    Geiranger
  51. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2328220
    destination:
    Sykkylven
  52. oid:
    2328220
    origin:
    Sykkylven
    did:
    2328232
    destination:
    Ålesund
  53. oid:
    2452175
    origin:
    Valldal
    did:
    2328220
    destination:
    Sykkylven

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.

AI agent? Read the complete navigation and programming guide.