Eidsnes ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T04:51:12Z.

Havn

havn_id:
2467316
navn:
Eidsnes ankring
kode:
NOZEA
type:
Ankerplass
kommune:
Alver
fylke:
Vestland
lat:
60.588433
lon:
5.426667

Port-call and departure connections

34 results

  1. oid:
    2328076
    origin:
    Storebø
    did:
    2467316
    destination:
    Eidsnes ankring
  2. oid:
    2447414
    origin:
    Austevoll
    did:
    2467316
    destination:
    Eidsnes ankring
  3. oid:
    2467326
    origin:
    Sandane ankring
    did:
    2467316
    destination:
    Eidsnes ankring
  4. oid:
    2328084
    origin:
    Florø
    did:
    2467316
    destination:
    Eidsnes ankring
  5. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467316
    destination:
    Eidsnes ankring
  6. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467316
    destination:
    Eidsnes ankring
  7. oid:
    2454528
    origin:
    Skålevik
    did:
    2467316
    destination:
    Eidsnes ankring
  8. oid:
    2447385
    origin:
    Skogsvåg
    did:
    2467316
    destination:
    Eidsnes ankring
  9. oid:
    2328078
    origin:
    Bergen
    did:
    2467316
    destination:
    Eidsnes ankring
  10. oid:
    2328078
    origin:
    Bergen
    did:
    2467316
    destination:
    Eidsnes ankring
  11. oid:
    2328078
    origin:
    Bergen
    did:
    2467316
    destination:
    Eidsnes ankring
  12. oid:
    2328078
    origin:
    Bergen
    did:
    2467316
    destination:
    Eidsnes ankring
  13. oid:
    2328078
    origin:
    Bergen
    did:
    2467316
    destination:
    Eidsnes ankring
  14. oid:
    2461773
    origin:
    Spildepollen
    did:
    2467316
    destination:
    Eidsnes ankring
  15. oid:
    2450267
    origin:
    Sunde
    did:
    2467316
    destination:
    Eidsnes ankring
  16. oid:
    2447779
    origin:
    Selbjørnsfjorden
    did:
    2467316
    destination:
    Eidsnes ankring
  17. oid:
    2447388
    origin:
    Haugsøytangen ankring
    did:
    2467316
    destination:
    Eidsnes ankring
  18. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  19. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  20. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  21. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  22. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  23. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  24. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447779
    destination:
    Selbjørnsfjorden
  25. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2457687
    destination:
    Lurefjorden
  26. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2461773
    destination:
    Spildepollen
  27. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2328078
    destination:
    Bergen
  28. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2454528
    destination:
    Skålevik
  29. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2328146
    destination:
    Gunhildvågen
  30. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2461754
    destination:
    Brekke
  31. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2457810
    destination:
    Hellesøy
  32. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447784
    destination:
    Fitjar
  33. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2447414
    destination:
    Austevoll
  34. oid:
    2467316
    origin:
    Eidsnes ankring
    did:
    2328128
    destination:
    Rubbestadneset

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.