Papenburg

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-05T01:21:53Z.

Havn

havn_id:
2328898
navn:
Papenburg
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
53.0666666666667
lon:
7.4

Port-call and departure connections

54 results

  1. oid:
    2328898
    origin:
    Papenburg
    did:
    2327969
    destination:
    Valberg - Kragerø
  2. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  3. oid:
    2328239
    origin:
    Tjeldbergodden
    did:
    2328898
    destination:
    Papenburg
  4. oid:
    2328898
    origin:
    Papenburg
    did:
    2450362
    destination:
    Strandvikflaket ankring
  5. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  6. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  7. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  8. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  9. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  10. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  11. oid:
    2328898
    origin:
    Papenburg
    did:
    2328012
    destination:
    Rekefjord
  12. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  13. oid:
    2328898
    origin:
    Papenburg
    did:
    2327995
    destination:
    Kristiansand
  14. oid:
    2328898
    origin:
    Papenburg
    did:
    2328089
    destination:
    Gudvangen
  15. oid:
    2328898
    origin:
    Papenburg
    did:
    2327908
    destination:
    Fredrikstad
  16. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  17. oid:
    2328898
    origin:
    Papenburg
    did:
    2328018
    destination:
    Hausvikstrand
  18. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  19. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  20. oid:
    2328898
    origin:
    Papenburg
    did:
    2328012
    destination:
    Rekefjord
  21. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  22. oid:
    2328898
    origin:
    Papenburg
    did:
    2447631
    destination:
    Lyngdal
  23. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  24. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2328898
    destination:
    Papenburg
  25. oid:
    2328898
    origin:
    Papenburg
    did:
    2328012
    destination:
    Rekefjord
  26. oid:
    2328898
    origin:
    Papenburg
    did:
    2328122
    destination:
    Tyssedal
  27. oid:
    2328898
    origin:
    Papenburg
    did:
    2328067
    destination:
    Storøya Øst
  28. oid:
    2328898
    origin:
    Papenburg
    did:
    2328067
    destination:
    Storøya Øst
  29. oid:
    2328898
    origin:
    Papenburg
    did:
    2328125
    destination:
    Sløvåg Industriområde
  30. oid:
    2328898
    origin:
    Papenburg
    did:
    2327904
    destination:
    Drammen
  31. oid:
    2328898
    origin:
    Papenburg
    did:
    2327908
    destination:
    Fredrikstad
  32. oid:
    2328898
    origin:
    Papenburg
    did:
    2328067
    destination:
    Storøya Øst
  33. oid:
    2328898
    origin:
    Papenburg
    did:
    2341694
    destination:
    Voll - Skien
  34. oid:
    2328898
    origin:
    Papenburg
    did:
    2466366
    destination:
    Byggnes - Karmsundet ankring
  35. oid:
    2328898
    origin:
    Papenburg
    did:
    2328082
    destination:
    Eikefet
  36. oid:
    2328898
    origin:
    Papenburg
    did:
    2328082
    destination:
    Eikefet
  37. oid:
    2328084
    origin:
    Florø
    did:
    2328898
    destination:
    Papenburg
  38. oid:
    2328898
    origin:
    Papenburg
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  39. oid:
    2328898
    origin:
    Papenburg
    did:
    2328125
    destination:
    Sløvåg Industriområde
  40. oid:
    2328125
    origin:
    Sløvåg Industriområde
    did:
    2328898
    destination:
    Papenburg
  41. oid:
    2328898
    origin:
    Papenburg
    did:
    2327988
    destination:
    Egersund
  42. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  43. oid:
    2328898
    origin:
    Papenburg
    did:
    2328012
    destination:
    Rekefjord
  44. oid:
    2328125
    origin:
    Sløvåg Industriområde
    did:
    2328898
    destination:
    Papenburg
  45. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2328898
    destination:
    Papenburg
  46. oid:
    2328898
    origin:
    Papenburg
    did:
    2328056
    destination:
    Jelsa
  47. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  48. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  49. oid:
    2328013
    origin:
    Sirevåg
    did:
    2328898
    destination:
    Papenburg
  50. oid:
    2328898
    origin:
    Papenburg
    did:
    2328069
    destination:
    Breiviga
  51. oid:
    2328898
    origin:
    Papenburg
    did:
    2328043
    destination:
    Sauda
  52. oid:
    2328898
    origin:
    Papenburg
    did:
    2328012
    destination:
    Rekefjord
  53. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2328898
    destination:
    Papenburg
  54. oid:
    2328125
    origin:
    Sløvåg Industriområde
    did:
    2328898
    destination:
    Papenburg

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.