Halsa ferjekai

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T01:55:40Z.

Havn

havn_id:
2464174
navn:
Halsa ferjekai
kode:
not reported by source
type:
Ferjekai
kommune:
Heim
fylke:
Trøndelag
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

15 results

  1. oid:
    2464103
    origin:
    Linge ferjekai
    did:
    2464174
    destination:
    Halsa ferjekai
  2. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328232
    destination:
    Ålesund
  3. oid:
    2328084
    origin:
    Florø
    did:
    2464174
    destination:
    Halsa ferjekai
  4. oid:
    2328232
    origin:
    Ålesund
    did:
    2464174
    destination:
    Halsa ferjekai
  5. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328084
    destination:
    Florø
  6. oid:
    2328181
    origin:
    Hjørungavåg
    did:
    2464174
    destination:
    Halsa ferjekai
  7. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328181
    destination:
    Hjørungavåg
  8. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328181
    destination:
    Hjørungavåg
  9. oid:
    2328181
    origin:
    Hjørungavåg
    did:
    2464174
    destination:
    Halsa ferjekai
  10. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328189
    destination:
    Kristiansund
  11. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2328189
    destination:
    Kristiansund
  12. oid:
    2328219
    origin:
    Surnadal
    did:
    2464174
    destination:
    Halsa ferjekai
  13. oid:
    2464174
    origin:
    Halsa ferjekai
    did:
    2464150
    destination:
    Sandvika ferjekai
  14. oid:
    2464150
    origin:
    Sandvika ferjekai
    did:
    2464174
    destination:
    Halsa ferjekai
  15. oid:
    2464181
    origin:
    Kvanne ferjekai
    did:
    2464174
    destination:
    Halsa ferjekai

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.