Greenland

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T13:05:21Z.

Havn

havn_id:
2328474
navn:
Greenland
kode:
not reported by source
type:
Land
kommune:
not reported by source
fylke:
not reported by source
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

35 results

  1. oid:
    2328474
    origin:
    Greenland
    did:
    2328078
    destination:
    Bergen
  2. oid:
    2332023
    origin:
    Ny-Ålesund
    did:
    2328474
    destination:
    Greenland
  3. oid:
    2332023
    origin:
    Ny-Ålesund
    did:
    2328474
    destination:
    Greenland
  4. oid:
    2328474
    origin:
    Greenland
    did:
    2328100
    destination:
    Måløy
  5. oid:
    2328100
    origin:
    Måløy
    did:
    2328474
    destination:
    Greenland
  6. oid:
    2328474
    origin:
    Greenland
    did:
    2329827
    destination:
    Isafjørdur - Høfn
  7. oid:
    2328361
    origin:
    Tromsø
    did:
    2328474
    destination:
    Greenland
  8. oid:
    2328459
    origin:
    Faroe Islands
    did:
    2328474
    destination:
    Greenland
  9. oid:
    2328474
    origin:
    Greenland
    did:
    2329819
    destination:
    Hafnarfjørdur
  10. oid:
    2329819
    origin:
    Hafnarfjørdur
    did:
    2328474
    destination:
    Greenland
  11. oid:
    2328474
    origin:
    Greenland
    did:
    2329819
    destination:
    Hafnarfjørdur
  12. oid:
    2329842
    origin:
    Reykjavik
    did:
    2328474
    destination:
    Greenland
  13. oid:
    2328474
    origin:
    Greenland
    did:
    2328232
    destination:
    Ålesund
  14. oid:
    2329819
    origin:
    Hafnarfjørdur
    did:
    2328474
    destination:
    Greenland
  15. oid:
    2328474
    origin:
    Greenland
    did:
    2328215
    destination:
    Steinshamn
  16. oid:
    2329819
    origin:
    Hafnarfjørdur
    did:
    2328474
    destination:
    Greenland
  17. oid:
    2328474
    origin:
    Greenland
    did:
    2329819
    destination:
    Hafnarfjørdur
  18. oid:
    2452223
    origin:
    Alvika
    did:
    2328474
    destination:
    Greenland
  19. oid:
    2329827
    origin:
    Isafjørdur - Høfn
    did:
    2328474
    destination:
    Greenland
  20. oid:
    2328474
    origin:
    Greenland
    did:
    2328078
    destination:
    Bergen
  21. oid:
    2328361
    origin:
    Tromsø
    did:
    2328474
    destination:
    Greenland
  22. oid:
    2328474
    origin:
    Greenland
    did:
    2328290
    destination:
    Sortland
  23. oid:
    2329849
    origin:
    Siglufjørdur - Høfn
    did:
    2328474
    destination:
    Greenland
  24. oid:
    2328474
    origin:
    Greenland
    did:
    2332022
    destination:
    Longyearbyen
  25. oid:
    2328078
    origin:
    Bergen
    did:
    2328474
    destination:
    Greenland
  26. oid:
    2328361
    origin:
    Tromsø
    did:
    2328474
    destination:
    Greenland
  27. oid:
    2332022
    origin:
    Longyearbyen
    did:
    2328474
    destination:
    Greenland
  28. oid:
    2328474
    origin:
    Greenland
    did:
    2332023
    destination:
    Ny-Ålesund
  29. oid:
    2328474
    origin:
    Greenland
    did:
    2328168
    destination:
    Ellingsøy
  30. oid:
    2328474
    origin:
    Greenland
    did:
    2328361
    destination:
    Tromsø
  31. oid:
    2328232
    origin:
    Ålesund
    did:
    2328474
    destination:
    Greenland
  32. oid:
    2328474
    origin:
    Greenland
    did:
    2328361
    destination:
    Tromsø
  33. oid:
    2462622
    origin:
    Jan Mayen
    did:
    2328474
    destination:
    Greenland
  34. oid:
    2328361
    origin:
    Tromsø
    did:
    2328474
    destination:
    Greenland
  35. oid:
    2328361
    origin:
    Tromsø
    did:
    2328474
    destination:
    Greenland

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.