Sævlandsvik

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T09:05:29Z.

Havn

havn_id:
2458485
navn:
Sævlandsvik
kode:
NOSVL
type:
Havn
kommune:
Karmøy
fylke:
Rogaland
lat:
59.271333
lon:
5.19175

Port-call and departure connections

53 results

  1. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328056
    destination:
    Jelsa
  2. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328045
    destination:
    Skudeneshavn
  3. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447404
    destination:
    Storesund
  4. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447404
    destination:
    Storesund
  5. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447404
    destination:
    Storesund
  6. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447660
    destination:
    Nordsjøen
  7. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2451826
    destination:
    Årdal - Hjelmeland
  8. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  9. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  10. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  11. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  12. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  13. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  14. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  15. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  16. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328054
    destination:
    Helle - Forsand
  17. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328065
    destination:
    Etne
  18. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447768
    destination:
    Forsand
  19. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447768
    destination:
    Forsand
  20. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447768
    destination:
    Forsand
  21. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2447768
    destination:
    Forsand
  22. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328063
    destination:
    Husøy - Karmøy
  23. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328063
    destination:
    Husøy - Karmøy
  24. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328063
    destination:
    Husøy - Karmøy
  25. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  26. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  27. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  28. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  29. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  30. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  31. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  32. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  33. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  34. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  35. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  36. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  37. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  38. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  39. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  40. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  41. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  42. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  43. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  44. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  45. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  46. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  47. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  48. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  49. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  50. oid:
    2328054
    origin:
    Helle - Forsand
    did:
    2458485
    destination:
    Sævlandsvik
  51. oid:
    2447660
    origin:
    Nordsjøen
    did:
    2458485
    destination:
    Sævlandsvik
  52. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328069
    destination:
    Breiviga
  53. oid:
    2458485
    origin:
    Sævlandsvik
    did:
    2328069
    destination:
    Breiviga

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.