Allemannsdata
Manual search

Helguvik

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T12:24:39Z.

Havn

havn_id:
2448497
navn:
Helguvik
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

35 results

  1. oid:
    2328361
    origin:
    Tromsø
    did:
    2448497
    destination:
    Helguvik
  2. oid:
    2328232
    origin:
    Ålesund
    did:
    2448497
    destination:
    Helguvik
  3. oid:
    2448497
    origin:
    Helguvik
    did:
    2327940
    destination:
    Langøya
  4. oid:
    2329838
    origin:
    Olafsvik
    did:
    2448497
    destination:
    Helguvik
  5. oid:
    2329859
    origin:
    Thorlakshofn
    did:
    2448497
    destination:
    Helguvik
  6. oid:
    2448497
    origin:
    Helguvik
    did:
    2329859
    destination:
    Thorlakshofn
  7. oid:
    2329819
    origin:
    Hafnarfjørdur
    did:
    2448497
    destination:
    Helguvik
  8. oid:
    2448497
    origin:
    Helguvik
    did:
    2329840
    destination:
    Patreksfjørdur - Høfn
  9. oid:
    2329859
    origin:
    Thorlakshofn
    did:
    2448497
    destination:
    Helguvik
  10. oid:
    2448497
    origin:
    Helguvik
    did:
    2329840
    destination:
    Patreksfjørdur - Høfn
  11. oid:
    2448497
    origin:
    Helguvik
    did:
    2329840
    destination:
    Patreksfjørdur - Høfn
  12. oid:
    2329859
    origin:
    Thorlakshofn
    did:
    2448497
    destination:
    Helguvik
  13. oid:
    2448497
    origin:
    Helguvik
    did:
    2329824
    destination:
    Husavik - Høfn
  14. oid:
    2329827
    origin:
    Isafjørdur - Høfn
    did:
    2448497
    destination:
    Helguvik
  15. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  16. oid:
    2328099
    origin:
    Mongstad
    did:
    2448497
    destination:
    Helguvik
  17. oid:
    2448497
    origin:
    Helguvik
    did:
    2328189
    destination:
    Kristiansund
  18. oid:
    2329861
    origin:
    Vestmannaeyjar - Høfn
    did:
    2448497
    destination:
    Helguvik
  19. oid:
    2448497
    origin:
    Helguvik
    did:
    2329857
    destination:
    Talknafjørdur/sveinseyri
  20. oid:
    2329811
    origin:
    Eskifjørdur - Høfn
    did:
    2448497
    destination:
    Helguvik
  21. oid:
    2448497
    origin:
    Helguvik
    did:
    2328056
    destination:
    Jelsa
  22. oid:
    2328050
    origin:
    Tau
    did:
    2448497
    destination:
    Helguvik
  23. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  24. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  25. oid:
    2448497
    origin:
    Helguvik
    did:
    2328227
    destination:
    Verdal
  26. oid:
    2448497
    origin:
    Helguvik
    did:
    2328123
    destination:
    Fonnesflaket ankring
  27. oid:
    2448497
    origin:
    Helguvik
    did:
    2328123
    destination:
    Fonnesflaket ankring
  28. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  29. oid:
    2448497
    origin:
    Helguvik
    did:
    2328123
    destination:
    Fonnesflaket ankring
  30. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  31. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  32. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  33. oid:
    2448497
    origin:
    Helguvik
    did:
    2328123
    destination:
    Fonnesflaket ankring
  34. oid:
    2448497
    origin:
    Helguvik
    did:
    2328099
    destination:
    Mongstad
  35. oid:
    2448497
    origin:
    Helguvik
    did:
    2328123
    destination:
    Fonnesflaket ankring

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.

AI agent? Read the complete navigation and programming guide.