Ringaskiddy

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:57:08Z.

Havn

havn_id:
2329771
navn:
Ringaskiddy
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
51.8333333333333
lon:
-8.31666666666667

Port-call and departure connections

25 results

  1. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2353312
    destination:
    Nesnaflaket ankring
  2. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2328131
    destination:
    Eide - Sotra
  3. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2328082
    destination:
    Eikefet
  4. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2328125
    destination:
    Sløvåg Industriområde
  5. oid:
    2328189
    origin:
    Kristiansund
    did:
    2329771
    destination:
    Ringaskiddy
  6. oid:
    2327955
    origin:
    Herøya
    did:
    2329771
    destination:
    Ringaskiddy
  7. oid:
    2327955
    origin:
    Herøya
    did:
    2329771
    destination:
    Ringaskiddy
  8. oid:
    2327955
    origin:
    Herøya
    did:
    2329771
    destination:
    Ringaskiddy
  9. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329771
    destination:
    Ringaskiddy
  10. oid:
    2328100
    origin:
    Måløy
    did:
    2329771
    destination:
    Ringaskiddy
  11. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  12. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  13. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  14. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  15. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  16. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  17. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  18. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  19. oid:
    2328262
    origin:
    Glomfjord
    did:
    2329771
    destination:
    Ringaskiddy
  20. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2327908
    destination:
    Fredrikstad
  21. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2327908
    destination:
    Fredrikstad
  22. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2327908
    destination:
    Fredrikstad
  23. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2327995
    destination:
    Kristiansand
  24. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2327974
    destination:
    Frierfjorden ankring
  25. oid:
    2329771
    origin:
    Ringaskiddy
    did:
    2328301
    destination:
    Finnfjordbotn

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.