Schiedam

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:57:55Z.

Havn

havn_id:
2330079
navn:
Schiedam
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
51.9169599
lon:
4.3988186

Port-call and departure connections

56 results

  1. oid:
    2330079
    origin:
    Schiedam
    did:
    2327904
    destination:
    Drammen
  2. oid:
    2330079
    origin:
    Schiedam
    did:
    2327904
    destination:
    Drammen
  3. oid:
    2330079
    origin:
    Schiedam
    did:
    2327904
    destination:
    Drammen
  4. oid:
    2330079
    origin:
    Schiedam
    did:
    2327904
    destination:
    Drammen
  5. oid:
    2330079
    origin:
    Schiedam
    did:
    2327904
    destination:
    Drammen
  6. oid:
    2330079
    origin:
    Schiedam
    did:
    2327911
    destination:
    Halden
  7. oid:
    2330079
    origin:
    Schiedam
    did:
    2328010
    destination:
    Maurholen
  8. oid:
    2330079
    origin:
    Schiedam
    did:
    2328010
    destination:
    Maurholen
  9. oid:
    2330079
    origin:
    Schiedam
    did:
    2328010
    destination:
    Maurholen
  10. oid:
    2330079
    origin:
    Schiedam
    did:
    2328056
    destination:
    Jelsa
  11. oid:
    2330079
    origin:
    Schiedam
    did:
    2328056
    destination:
    Jelsa
  12. oid:
    2330079
    origin:
    Schiedam
    did:
    2328056
    destination:
    Jelsa
  13. oid:
    2330079
    origin:
    Schiedam
    did:
    2327998
    destination:
    Mandal
  14. oid:
    2330079
    origin:
    Schiedam
    did:
    2451550
    destination:
    Stord base
  15. oid:
    2330079
    origin:
    Schiedam
    did:
    2328286
    destination:
    Sandnessjøen
  16. oid:
    2330079
    origin:
    Schiedam
    did:
    2328082
    destination:
    Eikefet
  17. oid:
    2330079
    origin:
    Schiedam
    did:
    2328082
    destination:
    Eikefet
  18. oid:
    2330079
    origin:
    Schiedam
    did:
    2327943
    destination:
    Brevik
  19. oid:
    2330079
    origin:
    Schiedam
    did:
    2327943
    destination:
    Brevik
  20. oid:
    2330079
    origin:
    Schiedam
    did:
    2327943
    destination:
    Brevik
  21. oid:
    2330079
    origin:
    Schiedam
    did:
    2328028
    destination:
    Haugesund
  22. oid:
    2330079
    origin:
    Schiedam
    did:
    2328028
    destination:
    Haugesund
  23. oid:
    2330079
    origin:
    Schiedam
    did:
    2328028
    destination:
    Haugesund
  24. oid:
    2330079
    origin:
    Schiedam
    did:
    2341458
    destination:
    Leirvik
  25. oid:
    2330079
    origin:
    Schiedam
    did:
    2327966
    destination:
    Snekkevik - Kragerø
  26. oid:
    2330079
    origin:
    Schiedam
    did:
    2450372
    destination:
    Duken og Kyrre ankring
  27. oid:
    2330079
    origin:
    Schiedam
    did:
    2327995
    destination:
    Kristiansand
  28. oid:
    2330079
    origin:
    Schiedam
    did:
    2328308
    destination:
    Halsa Meløy
  29. oid:
    2330079
    origin:
    Schiedam
    did:
    2328207
    destination:
    Orkanger
  30. oid:
    2330079
    origin:
    Schiedam
    did:
    2328089
    destination:
    Gudvangen
  31. oid:
    2330079
    origin:
    Schiedam
    did:
    2328223
    destination:
    Trondheim
  32. oid:
    2330079
    origin:
    Schiedam
    did:
    2328209
    destination:
    Rørvik
  33. oid:
    2330079
    origin:
    Schiedam
    did:
    2328012
    destination:
    Rekefjord
  34. oid:
    2328061
    origin:
    Mekjarvik
    did:
    2330079
    destination:
    Schiedam
  35. oid:
    2328023
    origin:
    Dusavik
    did:
    2330079
    destination:
    Schiedam
  36. oid:
    2466373
    origin:
    Ølen ankring
    did:
    2330079
    destination:
    Schiedam
  37. oid:
    2328028
    origin:
    Haugesund
    did:
    2330079
    destination:
    Schiedam
  38. oid:
    2328028
    origin:
    Haugesund
    did:
    2330079
    destination:
    Schiedam
  39. oid:
    2328028
    origin:
    Haugesund
    did:
    2330079
    destination:
    Schiedam
  40. oid:
    2451550
    origin:
    Stord base
    did:
    2330079
    destination:
    Schiedam
  41. oid:
    2327904
    origin:
    Drammen
    did:
    2330079
    destination:
    Schiedam
  42. oid:
    2330079
    origin:
    Schiedam
    did:
    2327926
    destination:
    Sarpsborg
  43. oid:
    2330079
    origin:
    Schiedam
    did:
    2327948
    destination:
    Larvik
  44. oid:
    2330079
    origin:
    Schiedam
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  45. oid:
    2330079
    origin:
    Schiedam
    did:
    2327922
    destination:
    Moss
  46. oid:
    2330079
    origin:
    Schiedam
    did:
    2328063
    destination:
    Husøy - Karmøy
  47. oid:
    2330079
    origin:
    Schiedam
    did:
    2328069
    destination:
    Breiviga
  48. oid:
    2330079
    origin:
    Schiedam
    did:
    2328069
    destination:
    Breiviga
  49. oid:
    2330079
    origin:
    Schiedam
    did:
    2328069
    destination:
    Breiviga
  50. oid:
    2330079
    origin:
    Schiedam
    did:
    2328061
    destination:
    Mekjarvik
  51. oid:
    2330079
    origin:
    Schiedam
    did:
    2447392
    destination:
    Knarrevik
  52. oid:
    2330079
    origin:
    Schiedam
    did:
    2447392
    destination:
    Knarrevik
  53. oid:
    2330079
    origin:
    Schiedam
    did:
    2328224
    destination:
    Ulsteinvik
  54. oid:
    2330079
    origin:
    Schiedam
    did:
    2328224
    destination:
    Ulsteinvik
  55. oid:
    2330079
    origin:
    Schiedam
    did:
    2458523
    destination:
    Gullaug - Drammen ankring
  56. oid:
    2330079
    origin:
    Schiedam
    did:
    2458523
    destination:
    Gullaug - Drammen ankring

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.