Allemannsdata
Manual search

Aurland

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T07:13:33Z.

Havn

havn_id:
2341267
navn:
Aurland
kode:
not reported by source
type:
Havn
kommune:
Aurland
fylke:
Vestland
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

30 results

  1. oid:
    2341267
    origin:
    Aurland
    did:
    2452222
    destination:
    Sløvåg
  2. oid:
    2451836
    origin:
    Listraumen
    did:
    2341267
    destination:
    Aurland
  3. oid:
    2341267
    origin:
    Aurland
    did:
    2451836
    destination:
    Listraumen
  4. oid:
    2451836
    origin:
    Listraumen
    did:
    2341267
    destination:
    Aurland
  5. oid:
    2341267
    origin:
    Aurland
    did:
    2451836
    destination:
    Listraumen
  6. oid:
    2451836
    origin:
    Listraumen
    did:
    2341267
    destination:
    Aurland
  7. oid:
    2341267
    origin:
    Aurland
    did:
    2451836
    destination:
    Listraumen
  8. oid:
    2451836
    origin:
    Listraumen
    did:
    2341267
    destination:
    Aurland
  9. oid:
    2341267
    origin:
    Aurland
    did:
    2452204
    destination:
    Ukjent lokasjon Norge
  10. oid:
    2450230
    origin:
    Eidsnes
    did:
    2341267
    destination:
    Aurland
  11. oid:
    2341267
    origin:
    Aurland
    did:
    2328096
    destination:
    Lærdal
  12. oid:
    2447768
    origin:
    Forsand
    did:
    2341267
    destination:
    Aurland
  13. oid:
    2341267
    origin:
    Aurland
    did:
    2452147
    destination:
    Kollsnes Øst
  14. oid:
    2328025
    origin:
    Forus
    did:
    2341267
    destination:
    Aurland
  15. oid:
    2341267
    origin:
    Aurland
    did:
    2328128
    destination:
    Rubbestadneset
  16. oid:
    2465652
    origin:
    Eidsnes steinkai
    did:
    2341267
    destination:
    Aurland
  17. oid:
    2341267
    origin:
    Aurland
    did:
    2458171
    destination:
    Seljestokken
  18. oid:
    2447768
    origin:
    Forsand
    did:
    2341267
    destination:
    Aurland
  19. oid:
    2341267
    origin:
    Aurland
    did:
    2458171
    destination:
    Seljestokken
  20. oid:
    2450230
    origin:
    Eidsnes
    did:
    2341267
    destination:
    Aurland
  21. oid:
    2341267
    origin:
    Aurland
    did:
    2447768
    destination:
    Forsand
  22. oid:
    2447768
    origin:
    Forsand
    did:
    2341267
    destination:
    Aurland
  23. oid:
    2341267
    origin:
    Aurland
    did:
    2451922
    destination:
    Gjøsundet
  24. oid:
    2447404
    origin:
    Storesund
    did:
    2341267
    destination:
    Aurland
  25. oid:
    2341267
    origin:
    Aurland
    did:
    2328100
    destination:
    Måløy
  26. oid:
    2447768
    origin:
    Forsand
    did:
    2341267
    destination:
    Aurland
  27. oid:
    2341267
    origin:
    Aurland
    did:
    2328085
    destination:
    Flåm
  28. oid:
    2467320
    origin:
    Gudvangen ankring
    did:
    2341267
    destination:
    Aurland
  29. oid:
    2328085
    origin:
    Flåm
    did:
    2341267
    destination:
    Aurland
  30. oid:
    2341267
    origin:
    Aurland
    did:
    2328077
    destination:
    Balestrand

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.