Eidesvik

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T07:40:43Z.

Havn

havn_id:
2460982
navn:
Eidesvik
kode:
NOBOM
type:
Havn
kommune:
Bømlo
fylke:
Vestland
lat:
59.5952
lon:
5.185083

Port-call and departure connections

54 results

  1. oid:
    2460982
    origin:
    Eidesvik
    did:
    2341292
    destination:
    Bømlo
  2. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  3. oid:
    2460982
    origin:
    Eidesvik
    did:
    2341292
    destination:
    Bømlo
  4. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  5. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328100
    destination:
    Måløy
  6. oid:
    2467314
    origin:
    Ombofjorden ankring
    did:
    2460982
    destination:
    Eidesvik
  7. oid:
    2460982
    origin:
    Eidesvik
    did:
    2467314
    destination:
    Ombofjorden ankring
  8. oid:
    2467314
    origin:
    Ombofjorden ankring
    did:
    2460982
    destination:
    Eidesvik
  9. oid:
    2460982
    origin:
    Eidesvik
    did:
    2461754
    destination:
    Brekke
  10. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328146
    destination:
    Gunhildvågen
  11. oid:
    2447784
    origin:
    Fitjar
    did:
    2460982
    destination:
    Eidesvik
  12. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328078
    destination:
    Bergen
  13. oid:
    2328115
    origin:
    Vadheim
    did:
    2460982
    destination:
    Eidesvik
  14. oid:
    2341292
    origin:
    Bømlo
    did:
    2460982
    destination:
    Eidesvik
  15. oid:
    2460982
    origin:
    Eidesvik
    did:
    2341292
    destination:
    Bømlo
  16. oid:
    2328128
    origin:
    Rubbestadneset
    did:
    2460982
    destination:
    Eidesvik
  17. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328086
    destination:
    Fusa
  18. oid:
    2460980
    origin:
    Brubakken
    did:
    2460982
    destination:
    Eidesvik
  19. oid:
    2460982
    origin:
    Eidesvik
    did:
    2460980
    destination:
    Brubakken
  20. oid:
    2450370
    origin:
    Byfjorden - Bergen
    did:
    2460982
    destination:
    Eidesvik
  21. oid:
    2328078
    origin:
    Bergen
    did:
    2460982
    destination:
    Eidesvik
  22. oid:
    2447404
    origin:
    Storesund
    did:
    2460982
    destination:
    Eidesvik
  23. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328086
    destination:
    Fusa
  24. oid:
    2465666
    origin:
    Årsnes
    did:
    2460982
    destination:
    Eidesvik
  25. oid:
    2460982
    origin:
    Eidesvik
    did:
    2346743
    destination:
    Jøsenfjorden
  26. oid:
    2346743
    origin:
    Jøsenfjorden
    did:
    2460982
    destination:
    Eidesvik
  27. oid:
    2460982
    origin:
    Eidesvik
    did:
    2341292
    destination:
    Bømlo
  28. oid:
    2341292
    origin:
    Bømlo
    did:
    2460982
    destination:
    Eidesvik
  29. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328111
    destination:
    Stord
  30. oid:
    2447404
    origin:
    Storesund
    did:
    2460982
    destination:
    Eidesvik
  31. oid:
    2460982
    origin:
    Eidesvik
    did:
    2341292
    destination:
    Bømlo
  32. oid:
    2341292
    origin:
    Bømlo
    did:
    2460982
    destination:
    Eidesvik
  33. oid:
    2460982
    origin:
    Eidesvik
    did:
    2447404
    destination:
    Storesund
  34. oid:
    2452137
    origin:
    Osnes - Vindafjord
    did:
    2460982
    destination:
    Eidesvik
  35. oid:
    2460982
    origin:
    Eidesvik
    did:
    2452137
    destination:
    Osnes - Vindafjord
  36. oid:
    2452137
    origin:
    Osnes - Vindafjord
    did:
    2460982
    destination:
    Eidesvik
  37. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  38. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  39. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  40. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  41. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  42. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  43. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  44. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  45. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  46. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  47. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  48. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  49. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  50. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2460982
    destination:
    Eidesvik
  51. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328076
    destination:
    Storebø
  52. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik
  53. oid:
    2460982
    origin:
    Eidesvik
    did:
    2328127
    destination:
    Langevåg
  54. oid:
    2328127
    origin:
    Langevåg
    did:
    2460982
    destination:
    Eidesvik

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.