Solvorn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:07:13Z.

Havn

havn_id:
2462559
navn:
Solvorn
kode:
NO888
type:
Ankerplass
kommune:
Luster
fylke:
Vestland
lat:
61.3
lon:
7.256667

Port-call and departure connections

31 results

  1. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  2. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  3. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  4. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  5. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  6. oid:
    2462559
    origin:
    Solvorn
    did:
    2328094
    destination:
    Kaupanger
  7. oid:
    2341392
    origin:
    Hermansverk
    did:
    2462559
    destination:
    Solvorn
  8. oid:
    2341587
    origin:
    Skjolden
    did:
    2462559
    destination:
    Solvorn
  9. oid:
    2466370
    origin:
    Lærdal ankring
    did:
    2462559
    destination:
    Solvorn
  10. oid:
    2467319
    origin:
    Flåm ankring
    did:
    2462559
    destination:
    Solvorn
  11. oid:
    2467320
    origin:
    Gudvangen ankring
    did:
    2462559
    destination:
    Solvorn
  12. oid:
    2467320
    origin:
    Gudvangen ankring
    did:
    2462559
    destination:
    Solvorn
  13. oid:
    2467320
    origin:
    Gudvangen ankring
    did:
    2462559
    destination:
    Solvorn
  14. oid:
    2328089
    origin:
    Gudvangen
    did:
    2462559
    destination:
    Solvorn
  15. oid:
    2458563
    origin:
    Nærøyfjorden
    did:
    2462559
    destination:
    Solvorn
  16. oid:
    2328077
    origin:
    Balestrand
    did:
    2462559
    destination:
    Solvorn
  17. oid:
    2328085
    origin:
    Flåm
    did:
    2462559
    destination:
    Solvorn
  18. oid:
    2328085
    origin:
    Flåm
    did:
    2462559
    destination:
    Solvorn
  19. oid:
    2328094
    origin:
    Kaupanger
    did:
    2462559
    destination:
    Solvorn
  20. oid:
    2328094
    origin:
    Kaupanger
    did:
    2462559
    destination:
    Solvorn
  21. oid:
    2328094
    origin:
    Kaupanger
    did:
    2462559
    destination:
    Solvorn
  22. oid:
    2328094
    origin:
    Kaupanger
    did:
    2462559
    destination:
    Solvorn
  23. oid:
    2462559
    origin:
    Solvorn
    did:
    2328077
    destination:
    Balestrand
  24. oid:
    2462559
    origin:
    Solvorn
    did:
    2328077
    destination:
    Balestrand
  25. oid:
    2462559
    origin:
    Solvorn
    did:
    2447403
    destination:
    Fjærland
  26. oid:
    2462559
    origin:
    Solvorn
    did:
    2447403
    destination:
    Fjærland
  27. oid:
    2462559
    origin:
    Solvorn
    did:
    2447403
    destination:
    Fjærland
  28. oid:
    2462559
    origin:
    Solvorn
    did:
    2447403
    destination:
    Fjærland
  29. oid:
    2462559
    origin:
    Solvorn
    did:
    2328109
    destination:
    Sogndal
  30. oid:
    2462559
    origin:
    Solvorn
    did:
    2457271
    destination:
    Fodnes
  31. oid:
    2462559
    origin:
    Solvorn
    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.