Ølve

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

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

Havn

havn_id:
2328130
navn:
Ølve
kode:
NOOLV
type:
Havn
kommune:
Kvinnherad
fylke:
Vestland
lat:
59.997367
lon:
5.79572

Port-call and departure connections

36 results

  1. oid:
    2328130
    origin:
    Ølve
    did:
    2328056
    destination:
    Jelsa
  2. oid:
    2328130
    origin:
    Ølve
    did:
    2328056
    destination:
    Jelsa
  3. oid:
    2328130
    origin:
    Ølve
    did:
    2328056
    destination:
    Jelsa
  4. oid:
    2328130
    origin:
    Ølve
    did:
    2328145
    destination:
    Kollsnes
  5. oid:
    2328130
    origin:
    Ølve
    did:
    2451550
    destination:
    Stord base
  6. oid:
    2328130
    origin:
    Ølve
    did:
    2328129
    destination:
    Ågotnes
  7. oid:
    2328130
    origin:
    Ølve
    did:
    2465924
    destination:
    Fanafjorden ankring
  8. oid:
    2328130
    origin:
    Ølve
    did:
    2465924
    destination:
    Fanafjorden ankring
  9. oid:
    2328130
    origin:
    Ølve
    did:
    2450267
    destination:
    Sunde
  10. oid:
    2447661
    origin:
    Offshoreinst. Nordsjøen
    did:
    2328130
    destination:
    Ølve
  11. oid:
    2447661
    origin:
    Offshoreinst. Nordsjøen
    did:
    2328130
    destination:
    Ølve
  12. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2328130
    destination:
    Ølve
  13. oid:
    2465652
    origin:
    Eidsnes steinkai
    did:
    2328130
    destination:
    Ølve
  14. oid:
    2450243
    origin:
    Høylandsbygda
    did:
    2328130
    destination:
    Ølve
  15. oid:
    2450243
    origin:
    Høylandsbygda
    did:
    2328130
    destination:
    Ølve
  16. oid:
    2450243
    origin:
    Høylandsbygda
    did:
    2328130
    destination:
    Ølve
  17. oid:
    2450230
    origin:
    Eidsnes
    did:
    2328130
    destination:
    Ølve
  18. oid:
    2341306
    origin:
    Dimmelsvik
    did:
    2328130
    destination:
    Ølve
  19. oid:
    2341458
    origin:
    Leirvik
    did:
    2328130
    destination:
    Ølve
  20. oid:
    2328028
    origin:
    Haugesund
    did:
    2328130
    destination:
    Ølve
  21. oid:
    2328129
    origin:
    Ågotnes
    did:
    2328130
    destination:
    Ølve
  22. oid:
    2457268
    origin:
    Halhjem
    did:
    2328130
    destination:
    Ølve
  23. oid:
    2451501
    origin:
    Klosterfjorden
    did:
    2328130
    destination:
    Ølve
  24. oid:
    2451501
    origin:
    Klosterfjorden
    did:
    2328130
    destination:
    Ølve
  25. oid:
    2467321
    origin:
    Eidfjord ankring
    did:
    2328130
    destination:
    Ølve
  26. oid:
    2328056
    origin:
    Jelsa
    did:
    2328130
    destination:
    Ølve
  27. oid:
    2328086
    origin:
    Fusa
    did:
    2328130
    destination:
    Ølve
  28. oid:
    2328130
    origin:
    Ølve
    did:
    2328078
    destination:
    Bergen
  29. oid:
    2328130
    origin:
    Ølve
    did:
    2447385
    destination:
    Skogsvåg
  30. oid:
    2328130
    origin:
    Ølve
    did:
    2450243
    destination:
    Høylandsbygda
  31. oid:
    2328130
    origin:
    Ølve
    did:
    2328106
    destination:
    Rosendal
  32. oid:
    2328130
    origin:
    Ølve
    did:
    2328054
    destination:
    Helle - Forsand
  33. oid:
    2328130
    origin:
    Ølve
    did:
    2447416
    destination:
    Hanøytangen
  34. oid:
    2328130
    origin:
    Ølve
    did:
    2458557
    destination:
    Bjoa
  35. oid:
    2328130
    origin:
    Ølve
    did:
    2447784
    destination:
    Fitjar
  36. oid:
    2328130
    origin:
    Ølve
    did:
    2447661
    destination:
    Offshoreinst. Nordsjøen

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.