Allemannsdata
Manual search

Flåm ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T05:31:13Z.

Havn

havn_id:
2467319
navn:
Flåm ankring
kode:
not reported by source
type:
Ankerplass
kommune:
Aurland
fylke:
Vestland
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

30 results

  1. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2328078
    destination:
    Bergen
  2. oid:
    2328173
    origin:
    Geiranger
    did:
    2467319
    destination:
    Flåm ankring
  3. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2328048
    destination:
    Stavanger
  4. oid:
    2462559
    origin:
    Solvorn
    did:
    2467319
    destination:
    Flåm ankring
  5. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2447478
    destination:
    Rutletangen
  6. oid:
    2458563
    origin:
    Nærøyfjorden
    did:
    2467319
    destination:
    Flåm ankring
  7. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  8. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2467319
    destination:
    Flåm ankring
  9. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2458563
    destination:
    Nærøyfjorden
  10. oid:
    2458563
    origin:
    Nærøyfjorden
    did:
    2467319
    destination:
    Flåm ankring
  11. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2328077
    destination:
    Balestrand
  12. oid:
    2328089
    origin:
    Gudvangen
    did:
    2467319
    destination:
    Flåm ankring
  13. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  14. oid:
    2447403
    origin:
    Fjærland
    did:
    2467319
    destination:
    Flåm ankring
  15. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467242
    destination:
    Leikanger
  16. oid:
    2466370
    origin:
    Lærdal ankring
    did:
    2467319
    destination:
    Flåm ankring
  17. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2328094
    destination:
    Kaupanger
  18. oid:
    2450232
    origin:
    Eivindvik
    did:
    2467319
    destination:
    Flåm ankring
  19. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  20. oid:
    2464230
    origin:
    Sandviksflaket ankring
    did:
    2467319
    destination:
    Flåm ankring
  21. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  22. oid:
    2328077
    origin:
    Balestrand
    did:
    2467319
    destination:
    Flåm ankring
  23. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  24. oid:
    2447403
    origin:
    Fjærland
    did:
    2467319
    destination:
    Flåm ankring
  25. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  26. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2467319
    destination:
    Flåm ankring
  27. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  28. oid:
    2465713
    origin:
    Finnafjorden ankring
    did:
    2467319
    destination:
    Flåm ankring
  29. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2467320
    destination:
    Gudvangen ankring
  30. oid:
    2328077
    origin:
    Balestrand
    did:
    2467319
    destination:
    Flåm ankring

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.