Røsthavet

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T08:45:09Z.

Havn

havn_id:
2353318
navn:
Røsthavet
kode:
NOZRT
type:
Sted i sjøen
kommune:
Røst
fylke:
Nordland
lat:
67.598233
lon:
12.392578

Port-call and departure connections

35 results

  1. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328361
    destination:
    Tromsø
  2. oid:
    2328100
    origin:
    Måløy
    did:
    2353318
    destination:
    Røsthavet
  3. oid:
    2353318
    origin:
    Røsthavet
    did:
    2450272
    destination:
    Træna
  4. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328251
    destination:
    Bodø
  5. oid:
    2328361
    origin:
    Tromsø
    did:
    2353318
    destination:
    Røsthavet
  6. oid:
    2328232
    origin:
    Ålesund
    did:
    2353318
    destination:
    Røsthavet
  7. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328290
    destination:
    Sortland
  8. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2353318
    destination:
    Røsthavet
  9. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328276
    destination:
    Moskenes
  10. oid:
    2328251
    origin:
    Bodø
    did:
    2353318
    destination:
    Røsthavet
  11. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328251
    destination:
    Bodø
  12. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328157
    destination:
    Averøy
  13. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328251
    destination:
    Bodø
  14. oid:
    2328361
    origin:
    Tromsø
    did:
    2353318
    destination:
    Røsthavet
  15. oid:
    2328251
    origin:
    Bodø
    did:
    2353318
    destination:
    Røsthavet
  16. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328232
    destination:
    Ålesund
  17. oid:
    2328361
    origin:
    Tromsø
    did:
    2353318
    destination:
    Røsthavet
  18. oid:
    2328361
    origin:
    Tromsø
    did:
    2353318
    destination:
    Røsthavet
  19. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  20. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  21. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  22. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  23. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  24. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  25. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  26. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  27. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  28. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  29. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  30. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet
  31. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  32. oid:
    2328251
    origin:
    Bodø
    did:
    2353318
    destination:
    Røsthavet
  33. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  34. oid:
    2353318
    origin:
    Røsthavet
    did:
    2328297
    destination:
    Værøy Sørlandsvågen
  35. oid:
    2328297
    origin:
    Værøy Sørlandsvågen
    did:
    2353318
    destination:
    Røsthavet

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.