Zwijndrecht

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T07:07:21Z.

Havn

havn_id:
2330099
navn:
Zwijndrecht
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
51.8105978
lon:
4.6272719

Port-call and departure connections

35 results

  1. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2327904
    destination:
    Drammen
  2. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2327958
    destination:
    Rafnes
  3. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2451460
    destination:
    Jøssingfjord
  4. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2451460
    destination:
    Jøssingfjord
  5. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  6. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  7. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  8. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  9. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  10. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  11. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  12. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  13. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  14. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  15. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  16. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  17. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  18. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  19. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  20. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  21. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  22. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  23. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  24. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  25. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  26. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  27. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  28. oid:
    2327958
    origin:
    Rafnes
    did:
    2330099
    destination:
    Zwijndrecht
  29. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2328012
    destination:
    Rekefjord
  30. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2328012
    destination:
    Rekefjord
  31. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2328012
    destination:
    Rekefjord
  32. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2328012
    destination:
    Rekefjord
  33. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2327926
    destination:
    Sarpsborg
  34. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2328069
    destination:
    Breiviga
  35. oid:
    2330099
    origin:
    Zwijndrecht
    did:
    2447392
    destination:
    Knarrevik

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.