Büsum

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T14:38:12Z.

Havn

havn_id:
2328709
navn:
Büsum
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
54.1346218
lon:
8.8585913

Port-call and departure connections

58 results

  1. oid:
    2328709
    origin:
    Büsum
    did:
    2328010
    destination:
    Maurholen
  2. oid:
    2328709
    origin:
    Büsum
    did:
    2328018
    destination:
    Hausvikstrand
  3. oid:
    2328709
    origin:
    Büsum
    did:
    2327949
    destination:
    Porsgrunn
  4. oid:
    2328709
    origin:
    Büsum
    did:
    2327988
    destination:
    Egersund
  5. oid:
    2452200
    origin:
    Skipavik-Gulen
    did:
    2328709
    destination:
    Büsum
  6. oid:
    2328069
    origin:
    Breiviga
    did:
    2328709
    destination:
    Büsum
  7. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  8. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  9. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  10. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  11. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  12. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  13. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  14. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  15. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  16. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  17. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  18. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  19. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  20. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  21. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  22. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  23. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  24. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  25. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  26. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  27. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  28. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  29. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  30. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  31. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  32. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  33. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  34. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  35. oid:
    2328012
    origin:
    Rekefjord
    did:
    2328709
    destination:
    Büsum
  36. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328709
    destination:
    Büsum
  37. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328709
    destination:
    Büsum
  38. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328709
    destination:
    Büsum
  39. oid:
    2328056
    origin:
    Jelsa
    did:
    2328709
    destination:
    Büsum
  40. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  41. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  42. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  43. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  44. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  45. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  46. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  47. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  48. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  49. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  50. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  51. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  52. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  53. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  54. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  55. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  56. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  57. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord
  58. oid:
    2328709
    origin:
    Büsum
    did:
    2328012
    destination:
    Rekefjord

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.