Setubal

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T17:38:07Z.

Havn

havn_id:
2330561
navn:
Setubal
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
38.5333333333333
lon:
-8.9

Port-call and departure connections

55 results

  1. oid:
    2330561
    origin:
    Setubal
    did:
    2328099
    destination:
    Mongstad
  2. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  3. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  4. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  5. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  6. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  7. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  8. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  9. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  10. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  11. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  12. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  13. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  14. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  15. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  16. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  17. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  18. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  19. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  20. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  21. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  22. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  23. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  24. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  25. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  26. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  27. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  28. oid:
    2330561
    origin:
    Setubal
    did:
    2328103
    destination:
    Odda
  29. oid:
    2330561
    origin:
    Setubal
    did:
    2327955
    destination:
    Herøya
  30. oid:
    2330561
    origin:
    Setubal
    did:
    2466366
    destination:
    Byggnes - Karmsundet ankring
  31. oid:
    2328069
    origin:
    Breiviga
    did:
    2330561
    destination:
    Setubal
  32. oid:
    2447404
    origin:
    Storesund
    did:
    2330561
    destination:
    Setubal
  33. oid:
    2341458
    origin:
    Leirvik
    did:
    2330561
    destination:
    Setubal
  34. oid:
    2341458
    origin:
    Leirvik
    did:
    2330561
    destination:
    Setubal
  35. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330561
    destination:
    Setubal
  36. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330561
    destination:
    Setubal
  37. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330561
    destination:
    Setubal
  38. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330561
    destination:
    Setubal
  39. oid:
    2341694
    origin:
    Voll - Skien
    did:
    2330561
    destination:
    Setubal
  40. oid:
    2341694
    origin:
    Voll - Skien
    did:
    2330561
    destination:
    Setubal
  41. oid:
    2330561
    origin:
    Setubal
    did:
    2328207
    destination:
    Orkanger
  42. oid:
    2330561
    origin:
    Setubal
    did:
    2328207
    destination:
    Orkanger
  43. oid:
    2330561
    origin:
    Setubal
    did:
    2328207
    destination:
    Orkanger
  44. oid:
    2330561
    origin:
    Setubal
    did:
    2328207
    destination:
    Orkanger
  45. oid:
    2330561
    origin:
    Setubal
    did:
    2447393
    destination:
    Straume
  46. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  47. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  48. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  49. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  50. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  51. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  52. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  53. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  54. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten
  55. oid:
    2330561
    origin:
    Setubal
    did:
    2327914
    destination:
    Horten

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.