Kyrksæterøra

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:58:00Z.

Havn

havn_id:
2328190
navn:
Kyrksæterøra
kode:
NOKYR
type:
Havn
kommune:
Heim
fylke:
Trøndelag
lat:
63.29071
lon:
9.09168

Port-call and departure connections

34 results

  1. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328239
    destination:
    Tjeldbergodden
  2. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328239
    destination:
    Tjeldbergodden
  3. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328239
    destination:
    Tjeldbergodden
  4. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328239
    destination:
    Tjeldbergodden
  5. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  6. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  7. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  8. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  9. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  10. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  11. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  12. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2447758
    destination:
    Ottersbogen
  13. oid:
    2328189
    origin:
    Kristiansund
    did:
    2328190
    destination:
    Kyrksæterøra
  14. oid:
    2328157
    origin:
    Averøy
    did:
    2328190
    destination:
    Kyrksæterøra
  15. oid:
    2328157
    origin:
    Averøy
    did:
    2328190
    destination:
    Kyrksæterøra
  16. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328190
    destination:
    Kyrksæterøra
  17. oid:
    2447386
    origin:
    Visnes - Eide
    did:
    2328190
    destination:
    Kyrksæterøra
  18. oid:
    2447386
    origin:
    Visnes - Eide
    did:
    2328190
    destination:
    Kyrksæterøra
  19. oid:
    2447386
    origin:
    Visnes - Eide
    did:
    2328190
    destination:
    Kyrksæterøra
  20. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  21. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  22. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  23. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  24. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  25. oid:
    2447758
    origin:
    Ottersbogen
    did:
    2328190
    destination:
    Kyrksæterøra
  26. oid:
    2328239
    origin:
    Tjeldbergodden
    did:
    2328190
    destination:
    Kyrksæterøra
  27. oid:
    2328239
    origin:
    Tjeldbergodden
    did:
    2328190
    destination:
    Kyrksæterøra
  28. oid:
    2328239
    origin:
    Tjeldbergodden
    did:
    2328190
    destination:
    Kyrksæterøra
  29. oid:
    2328239
    origin:
    Tjeldbergodden
    did:
    2328190
    destination:
    Kyrksæterøra
  30. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2457312
    destination:
    Bessaker
  31. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328218
    destination:
    Sunndalsøra
  32. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2451938
    destination:
    Skorgeneset
  33. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328157
    destination:
    Averøy
  34. oid:
    2328190
    origin:
    Kyrksæterøra
    did:
    2328156
    destination:
    Aure

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.