Cork

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T22:39:17Z.

Havn

havn_id:
2329767
navn:
Cork
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
51.8985143
lon:
-8.4756035

Port-call and departure connections

36 results

  1. oid:
    2353267
    origin:
    Rognan
    did:
    2329767
    destination:
    Cork
  2. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329767
    destination:
    Cork
  3. oid:
    2328231
    origin:
    Åheim
    did:
    2329767
    destination:
    Cork
  4. oid:
    2328231
    origin:
    Åheim
    did:
    2329767
    destination:
    Cork
  5. oid:
    2329767
    origin:
    Cork
    did:
    2328171
    destination:
    Follafoss
  6. oid:
    2329767
    origin:
    Cork
    did:
    2328125
    destination:
    Sløvåg Industriområde
  7. oid:
    2329767
    origin:
    Cork
    did:
    2328171
    destination:
    Follafoss
  8. oid:
    2329767
    origin:
    Cork
    did:
    2328034
    destination:
    Kårstø
  9. oid:
    2328034
    origin:
    Kårstø
    did:
    2329767
    destination:
    Cork
  10. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  11. oid:
    2329767
    origin:
    Cork
    did:
    2328082
    destination:
    Eikefet
  12. oid:
    2329767
    origin:
    Cork
    did:
    2328171
    destination:
    Follafoss
  13. oid:
    2329767
    origin:
    Cork
    did:
    2328123
    destination:
    Fonnesflaket ankring
  14. oid:
    2327955
    origin:
    Herøya
    did:
    2329767
    destination:
    Cork
  15. oid:
    2328231
    origin:
    Åheim
    did:
    2329767
    destination:
    Cork
  16. oid:
    2329767
    origin:
    Cork
    did:
    2328223
    destination:
    Trondheim
  17. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  18. oid:
    2329767
    origin:
    Cork
    did:
    2328120
    destination:
    Sture
  19. oid:
    2329767
    origin:
    Cork
    did:
    2328099
    destination:
    Mongstad
  20. oid:
    2329767
    origin:
    Cork
    did:
    2327955
    destination:
    Herøya
  21. oid:
    2328120
    origin:
    Sture
    did:
    2329767
    destination:
    Cork
  22. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  23. oid:
    2329767
    origin:
    Cork
    did:
    2328123
    destination:
    Fonnesflaket ankring
  24. oid:
    2329767
    origin:
    Cork
    did:
    2328239
    destination:
    Tjeldbergodden
  25. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  26. oid:
    2329767
    origin:
    Cork
    did:
    2328239
    destination:
    Tjeldbergodden
  27. oid:
    2327911
    origin:
    Halden
    did:
    2329767
    destination:
    Cork
  28. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  29. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  30. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  31. oid:
    2329767
    origin:
    Cork
    did:
    2328103
    destination:
    Odda
  32. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  33. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329767
    destination:
    Cork
  34. oid:
    2327911
    origin:
    Halden
    did:
    2329767
    destination:
    Cork
  35. oid:
    2329767
    origin:
    Cork
    did:
    2327908
    destination:
    Fredrikstad
  36. oid:
    2329767
    origin:
    Cork
    did:
    2328171
    destination:
    Follafoss

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.