Liabygda ferjekai

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T09:36:06Z.

Havn

havn_id:
2464108
navn:
Liabygda ferjekai
kode:
NOTDA
type:
Ferjekai
kommune:
Stranda
fylke:
Møre og Romsdal
lat:
62.308336
lon:
7.005887

Port-call and departure connections

30 results

  1. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2447629
    destination:
    Raudbergvika
  2. oid:
    2328179
    origin:
    Hellesylt
    did:
    2464108
    destination:
    Liabygda ferjekai
  3. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  4. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  5. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  6. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  7. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  8. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  9. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  10. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  11. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  12. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  13. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  14. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  15. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  16. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  17. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  18. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  19. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  20. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  21. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  22. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  23. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  24. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  25. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  26. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  27. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2464096
    destination:
    Stranda ferjekai
  28. oid:
    2466521
    origin:
    Geiranger kystrutekai
    did:
    2464108
    destination:
    Liabygda ferjekai
  29. oid:
    2464108
    origin:
    Liabygda ferjekai
    did:
    2466521
    destination:
    Geiranger kystrutekai
  30. oid:
    2464096
    origin:
    Stranda ferjekai
    did:
    2464108
    destination:
    Liabygda 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.