Allemannsdata
Manual search

King's Lynn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T09:55:48Z.

Havn

havn_id:
2329474
navn:
King's Lynn
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

34 results

  1. oid:
    2329474
    origin:
    King's Lynn
    did:
    2451460
    destination:
    Jøssingfjord
  2. oid:
    2329474
    origin:
    King's Lynn
    did:
    2451494
    destination:
    Stavanger Øst
  3. oid:
    2329474
    origin:
    King's Lynn
    did:
    2451494
    destination:
    Stavanger Øst
  4. oid:
    2329474
    origin:
    King's Lynn
    did:
    2327988
    destination:
    Egersund
  5. oid:
    2329474
    origin:
    King's Lynn
    did:
    2327988
    destination:
    Egersund
  6. oid:
    2329474
    origin:
    King's Lynn
    did:
    2447392
    destination:
    Knarrevik
  7. oid:
    2329474
    origin:
    King's Lynn
    did:
    2327998
    destination:
    Mandal
  8. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  9. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  10. oid:
    2329474
    origin:
    King's Lynn
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  11. oid:
    2464246
    origin:
    Husefest ankring
    did:
    2329474
    destination:
    King's Lynn
  12. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  13. oid:
    2329474
    origin:
    King's Lynn
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  14. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  15. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  16. oid:
    2329474
    origin:
    King's Lynn
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  17. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  18. oid:
    2329474
    origin:
    King's Lynn
    did:
    2467322
    destination:
    Hellefjorden ankring
  19. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328018
    destination:
    Hausvikstrand
  20. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  21. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  22. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  23. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  24. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  25. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  26. oid:
    2329474
    origin:
    King's Lynn
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  27. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  28. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328010
    destination:
    Maurholen
  29. oid:
    2329474
    origin:
    King's Lynn
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  30. oid:
    2329474
    origin:
    King's Lynn
    did:
    2451494
    destination:
    Stavanger Øst
  31. oid:
    2329474
    origin:
    King's Lynn
    did:
    2328146
    destination:
    Gunhildvågen
  32. oid:
    2329474
    origin:
    King's Lynn
    did:
    2451494
    destination:
    Stavanger Øst
  33. oid:
    2329474
    origin:
    King's Lynn
    did:
    2327923
    destination:
    Oslo
  34. oid:
    2329474
    origin:
    King's Lynn
    did:
    2447768
    destination:
    Forsand

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.

AI agent? Read the complete navigation and programming guide.