Hustadsundet

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T07:45:55Z.

Havn

havn_id:
2450395
navn:
Hustadsundet
kode:
NOZHW
type:
Sted i sjøen
kommune:
Gildeskål
fylke:
Nordland
lat:
67.1049
lon:
14.00908

Port-call and departure connections

34 results

  1. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328189
    destination:
    Kristiansund
  2. oid:
    2328232
    origin:
    Ålesund
    did:
    2450395
    destination:
    Hustadsundet
  3. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328234
    destination:
    Valsneset
  4. oid:
    2328234
    origin:
    Valsneset
    did:
    2450395
    destination:
    Hustadsundet
  5. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328234
    destination:
    Valsneset
  6. oid:
    2328234
    origin:
    Valsneset
    did:
    2450395
    destination:
    Hustadsundet
  7. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2353285
    destination:
    Tonnes
  8. oid:
    2328263
    origin:
    Hammerfall
    did:
    2450395
    destination:
    Hustadsundet
  9. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328234
    destination:
    Valsneset
  10. oid:
    2328234
    origin:
    Valsneset
    did:
    2450395
    destination:
    Hustadsundet
  11. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328308
    destination:
    Halsa Meløy
  12. oid:
    2467360
    origin:
    Gleinskallen ankring
    did:
    2450395
    destination:
    Hustadsundet
  13. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2450240
    destination:
    Herøy
  14. oid:
    2450240
    origin:
    Herøy
    did:
    2450395
    destination:
    Hustadsundet
  15. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328282
    destination:
    Reine
  16. oid:
    2328255
    origin:
    Brønnøysund
    did:
    2450395
    destination:
    Hustadsundet
  17. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2447761
    destination:
    Vågaholmen
  18. oid:
    2450353
    origin:
    Kilvik
    did:
    2450395
    destination:
    Hustadsundet
  19. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328356
    destination:
    Skjervøy
  20. oid:
    2328356
    origin:
    Skjervøy
    did:
    2450395
    destination:
    Hustadsundet
  21. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2450240
    destination:
    Herøy
  22. oid:
    2450240
    origin:
    Herøy
    did:
    2450395
    destination:
    Hustadsundet
  23. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2452164
    destination:
    Ågskardet
  24. oid:
    2447761
    origin:
    Vågaholmen
    did:
    2450395
    destination:
    Hustadsundet
  25. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2353256
    destination:
    Lovund
  26. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2450395
    destination:
    Hustadsundet
  27. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328286
    destination:
    Sandnessjøen
  28. oid:
    2328251
    origin:
    Bodø
    did:
    2450395
    destination:
    Hustadsundet
  29. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2447761
    destination:
    Vågaholmen
  30. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2450395
    destination:
    Hustadsundet
  31. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328251
    destination:
    Bodø
  32. oid:
    2328251
    origin:
    Bodø
    did:
    2450395
    destination:
    Hustadsundet
  33. oid:
    2450395
    origin:
    Hustadsundet
    did:
    2328251
    destination:
    Bodø
  34. oid:
    2353282
    origin:
    Stokkvågen
    did:
    2450395
    destination:
    Hustadsundet

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.