Nakskov

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T11:20:31Z.

Havn

havn_id:
2329080
navn:
Nakskov
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
54.833406
lon:
11.143724

Port-call and departure connections

35 results

  1. oid:
    2329080
    origin:
    Nakskov
    did:
    2327911
    destination:
    Halden
  2. oid:
    2329080
    origin:
    Nakskov
    did:
    2329094
    destination:
    Odense
  3. oid:
    2329080
    origin:
    Nakskov
    did:
    2327998
    destination:
    Mandal
  4. oid:
    2329080
    origin:
    Nakskov
    did:
    2327917
    destination:
    Kambo
  5. oid:
    2329080
    origin:
    Nakskov
    did:
    2328129
    destination:
    Ågotnes
  6. oid:
    2329080
    origin:
    Nakskov
    did:
    2447654
    destination:
    Halsnøy
  7. oid:
    2329080
    origin:
    Nakskov
    did:
    2341694
    destination:
    Voll - Skien
  8. oid:
    2329061
    origin:
    Kolding
    did:
    2329080
    destination:
    Nakskov
  9. oid:
    2327922
    origin:
    Moss
    did:
    2329080
    destination:
    Nakskov
  10. oid:
    2328989
    origin:
    Aabenraa
    did:
    2329080
    destination:
    Nakskov
  11. oid:
    2327926
    origin:
    Sarpsborg
    did:
    2329080
    destination:
    Nakskov
  12. oid:
    2328012
    origin:
    Rekefjord
    did:
    2329080
    destination:
    Nakskov
  13. oid:
    2328012
    origin:
    Rekefjord
    did:
    2329080
    destination:
    Nakskov
  14. oid:
    2328012
    origin:
    Rekefjord
    did:
    2329080
    destination:
    Nakskov
  15. oid:
    2327989
    origin:
    Eydehavn - Arendal
    did:
    2329080
    destination:
    Nakskov
  16. oid:
    2341694
    origin:
    Voll - Skien
    did:
    2329080
    destination:
    Nakskov
  17. oid:
    2327988
    origin:
    Egersund
    did:
    2329080
    destination:
    Nakskov
  18. oid:
    2328018
    origin:
    Hausvikstrand
    did:
    2329080
    destination:
    Nakskov
  19. oid:
    2447654
    origin:
    Halsnøy
    did:
    2329080
    destination:
    Nakskov
  20. oid:
    2328082
    origin:
    Eikefet
    did:
    2329080
    destination:
    Nakskov
  21. oid:
    2327998
    origin:
    Mandal
    did:
    2329080
    destination:
    Nakskov
  22. oid:
    2328056
    origin:
    Jelsa
    did:
    2329080
    destination:
    Nakskov
  23. oid:
    2327904
    origin:
    Drammen
    did:
    2329080
    destination:
    Nakskov
  24. oid:
    2327904
    origin:
    Drammen
    did:
    2329080
    destination:
    Nakskov
  25. oid:
    2327904
    origin:
    Drammen
    did:
    2329080
    destination:
    Nakskov
  26. oid:
    2329080
    origin:
    Nakskov
    did:
    2327969
    destination:
    Valberg - Kragerø
  27. oid:
    2329080
    origin:
    Nakskov
    did:
    2451494
    destination:
    Stavanger Øst
  28. oid:
    2329080
    origin:
    Nakskov
    did:
    2327939
    destination:
    Moss Nord
  29. oid:
    2329080
    origin:
    Nakskov
    did:
    2328012
    destination:
    Rekefjord
  30. oid:
    2329080
    origin:
    Nakskov
    did:
    2327974
    destination:
    Frierfjorden ankring
  31. oid:
    2329080
    origin:
    Nakskov
    did:
    2328070
    destination:
    Fiskå - Strand
  32. oid:
    2329080
    origin:
    Nakskov
    did:
    2327948
    destination:
    Larvik
  33. oid:
    2329080
    origin:
    Nakskov
    did:
    2451938
    destination:
    Skorgeneset
  34. oid:
    2329080
    origin:
    Nakskov
    did:
    2327923
    destination:
    Oslo
  35. oid:
    2329080
    origin:
    Nakskov
    did:
    2330496
    destination:
    Gdansk

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.