Uggdal

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:49:59Z.

Havn

havn_id:
2457123
navn:
Uggdal
kode:
NOTYN
type:
Havn
kommune:
Tysnes
fylke:
Vestland
lat:
59.995
lon:
5.49

Port-call and departure connections

36 results

  1. oid:
    2328128
    origin:
    Rubbestadneset
    did:
    2457123
    destination:
    Uggdal
  2. oid:
    2447473
    origin:
    Utne
    did:
    2457123
    destination:
    Uggdal
  3. oid:
    2447473
    origin:
    Utne
    did:
    2457123
    destination:
    Uggdal
  4. oid:
    2451826
    origin:
    Årdal - Hjelmeland
    did:
    2457123
    destination:
    Uggdal
  5. oid:
    2450230
    origin:
    Eidsnes
    did:
    2457123
    destination:
    Uggdal
  6. oid:
    2450230
    origin:
    Eidsnes
    did:
    2457123
    destination:
    Uggdal
  7. oid:
    2450230
    origin:
    Eidsnes
    did:
    2457123
    destination:
    Uggdal
  8. oid:
    2341306
    origin:
    Dimmelsvik
    did:
    2457123
    destination:
    Uggdal
  9. oid:
    2457009
    origin:
    Hordvik
    did:
    2457123
    destination:
    Uggdal
  10. oid:
    2457009
    origin:
    Hordvik
    did:
    2457123
    destination:
    Uggdal
  11. oid:
    2341665
    origin:
    Ullensvang
    did:
    2457123
    destination:
    Uggdal
  12. oid:
    2328129
    origin:
    Ågotnes
    did:
    2457123
    destination:
    Uggdal
  13. oid:
    2451501
    origin:
    Klosterfjorden
    did:
    2457123
    destination:
    Uggdal
  14. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  15. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  16. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  17. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  18. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  19. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2457123
    destination:
    Uggdal
  20. oid:
    2457123
    origin:
    Uggdal
    did:
    2341306
    destination:
    Dimmelsvik
  21. oid:
    2457123
    origin:
    Uggdal
    did:
    2447404
    destination:
    Storesund
  22. oid:
    2457123
    origin:
    Uggdal
    did:
    2447404
    destination:
    Storesund
  23. oid:
    2457123
    origin:
    Uggdal
    did:
    2447404
    destination:
    Storesund
  24. oid:
    2457123
    origin:
    Uggdal
    did:
    2447404
    destination:
    Storesund
  25. oid:
    2457123
    origin:
    Uggdal
    did:
    2450230
    destination:
    Eidsnes
  26. oid:
    2457123
    origin:
    Uggdal
    did:
    2451501
    destination:
    Klosterfjorden
  27. oid:
    2457123
    origin:
    Uggdal
    did:
    2330316
    destination:
    Sölvesborg
  28. oid:
    2457123
    origin:
    Uggdal
    did:
    2328054
    destination:
    Helle - Forsand
  29. oid:
    2457123
    origin:
    Uggdal
    did:
    2328054
    destination:
    Helle - Forsand
  30. oid:
    2457123
    origin:
    Uggdal
    did:
    2447768
    destination:
    Forsand
  31. oid:
    2457123
    origin:
    Uggdal
    did:
    2328069
    destination:
    Breiviga
  32. oid:
    2457123
    origin:
    Uggdal
    did:
    2328069
    destination:
    Breiviga
  33. oid:
    2457123
    origin:
    Uggdal
    did:
    2341424
    destination:
    Kinsarvik
  34. oid:
    2457123
    origin:
    Uggdal
    did:
    2341424
    destination:
    Kinsarvik
  35. oid:
    2457123
    origin:
    Uggdal
    did:
    2341424
    destination:
    Kinsarvik
  36. oid:
    2457123
    origin:
    Uggdal
    did:
    2456444
    destination:
    Tyssebotn

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.