Hellmobotn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

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

Havn

havn_id:
2447680
navn:
Hellmobotn
kode:
NOZHP
type:
Sted i sjøen
kommune:
Hamarøy
fylke:
Nordland
lat:
67.81852
lon:
16.51076

Port-call and departure connections

33 results

  1. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328286
    destination:
    Sandnessjøen
  2. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328286
    destination:
    Sandnessjøen
  3. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328262
    destination:
    Glomfjord
  4. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328256
    destination:
    Drag
  5. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328300
    destination:
    Bjerkvik
  6. oid:
    2328258
    origin:
    Evenestangen
    did:
    2447680
    destination:
    Hellmobotn
  7. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  8. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  9. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  10. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  11. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  12. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  13. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  14. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2447680
    destination:
    Hellmobotn
  15. oid:
    2328256
    origin:
    Drag
    did:
    2447680
    destination:
    Hellmobotn
  16. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2447680
    destination:
    Hellmobotn
  17. oid:
    2328272
    origin:
    Lødingen
    did:
    2447680
    destination:
    Hellmobotn
  18. oid:
    2457042
    origin:
    Liland
    did:
    2447680
    destination:
    Hellmobotn
  19. oid:
    2328209
    origin:
    Rørvik
    did:
    2447680
    destination:
    Hellmobotn
  20. oid:
    2328251
    origin:
    Bodø
    did:
    2447680
    destination:
    Hellmobotn
  21. oid:
    2328251
    origin:
    Bodø
    did:
    2447680
    destination:
    Hellmobotn
  22. oid:
    2457511
    origin:
    Ramberg
    did:
    2447680
    destination:
    Hellmobotn
  23. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2353264
    destination:
    Ørnes
  24. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2451806
    destination:
    Fiskefjord ankring
  25. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328308
    destination:
    Halsa Meløy
  26. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2457042
    destination:
    Liland
  27. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328251
    destination:
    Bodø
  28. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2466378
    destination:
    Narvik - Herjangen ankring
  29. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2466378
    destination:
    Narvik - Herjangen ankring
  30. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328157
    destination:
    Averøy
  31. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328157
    destination:
    Averøy
  32. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328258
    destination:
    Evenestangen
  33. oid:
    2447680
    origin:
    Hellmobotn
    did:
    2328189
    destination:
    Kristiansund

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.