Nuuk (Godthaab)

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T09:47:22Z.

Havn

havn_id:
2337318
navn:
Nuuk (Godthaab)
kode:
not reported by source
type:
Havn
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

9 results

  1. oid:
    2337318
    origin:
    Nuuk (Godthaab)
    did:
    2447771
    destination:
    Tromsø ankring
  2. oid:
    2447474
    origin:
    Vedavågen
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  3. oid:
    2458171
    origin:
    Seljestokken
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  4. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  5. oid:
    2328131
    origin:
    Eide - Sotra
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  6. oid:
    2337318
    origin:
    Nuuk (Godthaab)
    did:
    2327997
    destination:
    Lillesand
  7. oid:
    2337318
    origin:
    Nuuk (Godthaab)
    did:
    2332022
    destination:
    Longyearbyen
  8. oid:
    2451567
    origin:
    Stokksund
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  9. oid:
    2332022
    origin:
    Longyearbyen
    did:
    2337318
    destination:
    Nuuk (Godthaab)

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.