Søre Hillegrunnen ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:43:09Z.

Havn

havn_id:
2467332
navn:
Søre Hillegrunnen ankring
kode:
NOZH3
type:
Ankerplass
kommune:
Kvinnherad
fylke:
Vestland
lat:
59.78115
lon:
5.584267

Port-call and departure connections

48 results

  1. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328086
    destination:
    Fusa
  2. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328086
    destination:
    Fusa
  3. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328086
    destination:
    Fusa
  4. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2452198
    destination:
    Bøvågen - Karmøy
  5. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328234
    destination:
    Valsneset
  6. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328129
    destination:
    Ågotnes
  7. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2341458
    destination:
    Leirvik
  8. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2461092
    destination:
    Høyevarde - Karmsundet ankring
  9. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2461773
    destination:
    Spildepollen
  10. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2461773
    destination:
    Spildepollen
  11. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328078
    destination:
    Bergen
  12. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2450370
    destination:
    Byfjorden - Bergen
  13. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328232
    destination:
    Ålesund
  14. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2467328
    destination:
    Svanøya vest ankring
  15. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328146
    destination:
    Gunhildvågen
  16. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328146
    destination:
    Gunhildvågen
  17. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328146
    destination:
    Gunhildvågen
  18. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328146
    destination:
    Gunhildvågen
  19. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328108
    destination:
    Samnanger
  20. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328108
    destination:
    Samnanger
  21. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2447414
    destination:
    Austevoll
  22. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2457098
    destination:
    Bekkjarvik
  23. oid:
    2328128
    origin:
    Rubbestadneset
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  24. oid:
    2341292
    origin:
    Bømlo
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  25. oid:
    2328076
    origin:
    Storebø
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  26. oid:
    2454606
    origin:
    Dommersnes
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  27. oid:
    2447414
    origin:
    Austevoll
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  28. oid:
    2447414
    origin:
    Austevoll
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  29. oid:
    2447414
    origin:
    Austevoll
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  30. oid:
    2447784
    origin:
    Fitjar
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  31. oid:
    2328227
    origin:
    Verdal
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  32. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  33. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  34. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  35. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  36. oid:
    2450370
    origin:
    Byfjorden - Bergen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  37. oid:
    2450370
    origin:
    Byfjorden - Bergen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  38. oid:
    2447393
    origin:
    Straume
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  39. oid:
    2341458
    origin:
    Leirvik
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  40. oid:
    2341458
    origin:
    Leirvik
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  41. oid:
    2341458
    origin:
    Leirvik
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  42. oid:
    2330477
    origin:
    Rotterdam
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  43. oid:
    2447654
    origin:
    Halsnøy
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  44. oid:
    2450231
    origin:
    Eikelandsosen
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  45. oid:
    2328086
    origin:
    Fusa
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  46. oid:
    2328086
    origin:
    Fusa
    did:
    2467332
    destination:
    Søre Hillegrunnen ankring
  47. oid:
    2467332
    origin:
    Søre Hillegrunnen ankring
    did:
    2328128
    destination:
    Rubbestadneset
  48. oid:
    2467332
    origin:
    Søre Hillegrunnen 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.