Visund

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:11:29Z.

Havn

havn_id:
2454932
navn:
Visund
kode:
not reported by source
type:
Offshoreinstallasjon
kommune:
not reported by source
fylke:
not reported by source
lat:
61.4666666666667
lon:
2.5

Port-call and departure connections

30 results

  1. oid:
    2454932
    origin:
    Visund
    did:
    2328240
    destination:
    Liavåg
  2. oid:
    2454932
    origin:
    Visund
    did:
    2329045
    destination:
    Hirtshals
  3. oid:
    2454932
    origin:
    Visund
    did:
    2328129
    destination:
    Ågotnes
  4. oid:
    2454932
    origin:
    Visund
    did:
    2327988
    destination:
    Egersund
  5. oid:
    2454932
    origin:
    Visund
    did:
    2328236
    destination:
    Eggesbønes
  6. oid:
    2328084
    origin:
    Florø
    did:
    2454932
    destination:
    Visund
  7. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  8. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  9. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  10. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  11. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  12. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  13. oid:
    2328147
    origin:
    Botnaneset - Flora
    did:
    2454932
    destination:
    Visund
  14. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2454932
    destination:
    Visund
  15. oid:
    2328048
    origin:
    Stavanger
    did:
    2454932
    destination:
    Visund
  16. oid:
    2328100
    origin:
    Måløy
    did:
    2454932
    destination:
    Visund
  17. oid:
    2328361
    origin:
    Tromsø
    did:
    2454932
    destination:
    Visund
  18. oid:
    2328240
    origin:
    Liavåg
    did:
    2454932
    destination:
    Visund
  19. oid:
    2451550
    origin:
    Stord base
    did:
    2454932
    destination:
    Visund
  20. oid:
    2328131
    origin:
    Eide - Sotra
    did:
    2454932
    destination:
    Visund
  21. oid:
    2454932
    origin:
    Visund
    did:
    2328048
    destination:
    Stavanger
  22. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  23. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  24. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  25. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  26. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  27. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  28. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  29. oid:
    2454932
    origin:
    Visund
    did:
    2328147
    destination:
    Botnaneset - Flora
  30. oid:
    2454932
    origin:
    Visund
    did:
    2328084
    destination:
    Florø

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.