Hermansverk

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T02:40:07Z.

Havn

havn_id:
2341392
navn:
Hermansverk
kode:
NOHER
type:
Havn
kommune:
Sogndal
fylke:
Vestland
lat:
61.18423
lon:
6.84903

Port-call and departure connections

30 results

  1. oid:
    2341392
    origin:
    Hermansverk
    did:
    2451549
    destination:
    Vatlestraumen
  2. oid:
    2341392
    origin:
    Hermansverk
    did:
    2328094
    destination:
    Kaupanger
  3. oid:
    2341392
    origin:
    Hermansverk
    did:
    2328094
    destination:
    Kaupanger
  4. oid:
    2341392
    origin:
    Hermansverk
    did:
    2462559
    destination:
    Solvorn
  5. oid:
    2341392
    origin:
    Hermansverk
    did:
    2447744
    destination:
    Fensfjorden
  6. oid:
    2341392
    origin:
    Hermansverk
    did:
    2451939
    destination:
    Sævareid
  7. oid:
    2341392
    origin:
    Hermansverk
    did:
    2328100
    destination:
    Måløy
  8. oid:
    2341392
    origin:
    Hermansverk
    did:
    2451562
    destination:
    Sognefjorden
  9. oid:
    2341392
    origin:
    Hermansverk
    did:
    2458563
    destination:
    Nærøyfjorden
  10. oid:
    2341392
    origin:
    Hermansverk
    did:
    2461182
    destination:
    Vindafjord
  11. oid:
    2341392
    origin:
    Hermansverk
    did:
    2467320
    destination:
    Gudvangen ankring
  12. oid:
    2341392
    origin:
    Hermansverk
    did:
    2450397
    destination:
    Bjordal
  13. oid:
    2341392
    origin:
    Hermansverk
    did:
    2450397
    destination:
    Bjordal
  14. oid:
    2341392
    origin:
    Hermansverk
    did:
    2450397
    destination:
    Bjordal
  15. oid:
    2341392
    origin:
    Hermansverk
    did:
    2328115
    destination:
    Vadheim
  16. oid:
    2450397
    origin:
    Bjordal
    did:
    2341392
    destination:
    Hermansverk
  17. oid:
    2450397
    origin:
    Bjordal
    did:
    2341392
    destination:
    Hermansverk
  18. oid:
    2447784
    origin:
    Fitjar
    did:
    2341392
    destination:
    Hermansverk
  19. oid:
    2328084
    origin:
    Florø
    did:
    2341392
    destination:
    Hermansverk
  20. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2341392
    destination:
    Hermansverk
  21. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2341392
    destination:
    Hermansverk
  22. oid:
    2467320
    origin:
    Gudvangen ankring
    did:
    2341392
    destination:
    Hermansverk
  23. oid:
    2447385
    origin:
    Skogsvåg
    did:
    2341392
    destination:
    Hermansverk
  24. oid:
    2328078
    origin:
    Bergen
    did:
    2341392
    destination:
    Hermansverk
  25. oid:
    2447478
    origin:
    Rutletangen
    did:
    2341392
    destination:
    Hermansverk
  26. oid:
    2328151
    origin:
    Vågsfjorden
    did:
    2341392
    destination:
    Hermansverk
  27. oid:
    2328100
    origin:
    Måløy
    did:
    2341392
    destination:
    Hermansverk
  28. oid:
    2328192
    origin:
    Larsnes
    did:
    2341392
    destination:
    Hermansverk
  29. oid:
    2328086
    origin:
    Fusa
    did:
    2341392
    destination:
    Hermansverk
  30. oid:
    2467242
    origin:
    Leikanger
    did:
    2341392
    destination:
    Hermansverk

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.