Allemannsdata
Manual search

Seydisfjørdur

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T02:51:56Z.

Havn

havn_id:
2329848
navn:
Seydisfjørdur
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

23 results

  1. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328232
    destination:
    Ålesund
  2. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328369
    destination:
    Bergeneset
  3. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328158
    destination:
    Bjugn
  4. oid:
    2328078
    origin:
    Bergen
    did:
    2329848
    destination:
    Seydisfjørdur
  5. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2462622
    destination:
    Jan Mayen
  6. oid:
    2462622
    origin:
    Jan Mayen
    did:
    2329848
    destination:
    Seydisfjørdur
  7. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2462622
    destination:
    Jan Mayen
  8. oid:
    2462622
    origin:
    Jan Mayen
    did:
    2329848
    destination:
    Seydisfjørdur
  9. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2462622
    destination:
    Jan Mayen
  10. oid:
    2328232
    origin:
    Ålesund
    did:
    2329848
    destination:
    Seydisfjørdur
  11. oid:
    2328104
    origin:
    Olden
    did:
    2329848
    destination:
    Seydisfjørdur
  12. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328010
    destination:
    Maurholen
  13. oid:
    2328232
    origin:
    Ålesund
    did:
    2329848
    destination:
    Seydisfjørdur
  14. oid:
    2328078
    origin:
    Bergen
    did:
    2329848
    destination:
    Seydisfjørdur
  15. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328078
    destination:
    Bergen
  16. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328078
    destination:
    Bergen
  17. oid:
    2328232
    origin:
    Ålesund
    did:
    2329848
    destination:
    Seydisfjørdur
  18. oid:
    2328042
    origin:
    Sandnes
    did:
    2329848
    destination:
    Seydisfjørdur
  19. oid:
    2328232
    origin:
    Ålesund
    did:
    2329848
    destination:
    Seydisfjørdur
  20. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328232
    destination:
    Ålesund
  21. oid:
    2329848
    origin:
    Seydisfjørdur
    did:
    2328173
    destination:
    Geiranger
  22. oid:
    2328078
    origin:
    Bergen
    did:
    2329848
    destination:
    Seydisfjørdur
  23. oid:
    2452204
    origin:
    Ukjent lokasjon Norge
    did:
    2329848
    destination:
    Seydisfjørdur

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.