Skien

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:49:49Z.

Havn

havn_id:
2327951
navn:
Skien
kode:
NOSKE
type:
Havn
kommune:
Skien
fylke:
Telemark
lat:
59.20128
lon:
9.61108

Port-call and departure connections

57 results

  1. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  2. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  3. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  4. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  5. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  6. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  7. oid:
    2327951
    origin:
    Skien
    did:
    2327911
    destination:
    Halden
  8. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  9. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  10. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  11. oid:
    2330507
    origin:
    Gdynia
    did:
    2327951
    destination:
    Skien
  12. oid:
    2330507
    origin:
    Gdynia
    did:
    2327951
    destination:
    Skien
  13. oid:
    2327948
    origin:
    Larvik
    did:
    2327951
    destination:
    Skien
  14. oid:
    2327948
    origin:
    Larvik
    did:
    2327951
    destination:
    Skien
  15. oid:
    2327948
    origin:
    Larvik
    did:
    2327951
    destination:
    Skien
  16. oid:
    2327926
    origin:
    Sarpsborg
    did:
    2327951
    destination:
    Skien
  17. oid:
    2327926
    origin:
    Sarpsborg
    did:
    2327951
    destination:
    Skien
  18. oid:
    2328048
    origin:
    Stavanger
    did:
    2327951
    destination:
    Skien
  19. oid:
    2327974
    origin:
    Frierfjorden ankring
    did:
    2327951
    destination:
    Skien
  20. oid:
    2328784
    origin:
    Heiligenhafen
    did:
    2327951
    destination:
    Skien
  21. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  22. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  23. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  24. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  25. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  26. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  27. oid:
    2330484
    origin:
    Stettin
    did:
    2327951
    destination:
    Skien
  28. oid:
    2327913
    origin:
    Holmestrand
    did:
    2327951
    destination:
    Skien
  29. oid:
    2332012
    origin:
    Køping
    did:
    2327951
    destination:
    Skien
  30. oid:
    2329639
    origin:
    South Shields
    did:
    2327951
    destination:
    Skien
  31. oid:
    2330252
    origin:
    Malmø
    did:
    2327951
    destination:
    Skien
  32. oid:
    2447401
    origin:
    Bøneset - Karmøy
    did:
    2327951
    destination:
    Skien
  33. oid:
    2327934
    origin:
    Tønsberg
    did:
    2327951
    destination:
    Skien
  34. oid:
    2327951
    origin:
    Skien
    did:
    2330498
    destination:
    Ukjent lokasjon, ukjent land
  35. oid:
    2327951
    origin:
    Skien
    did:
    2330498
    destination:
    Ukjent lokasjon, ukjent land
  36. oid:
    2327951
    origin:
    Skien
    did:
    2330498
    destination:
    Ukjent lokasjon, ukjent land
  37. oid:
    2327951
    origin:
    Skien
    did:
    2330498
    destination:
    Ukjent lokasjon, ukjent land
  38. oid:
    2327951
    origin:
    Skien
    did:
    2330498
    destination:
    Ukjent lokasjon, ukjent land
  39. oid:
    2327951
    origin:
    Skien
    did:
    2328920
    destination:
    Rostock
  40. oid:
    2327951
    origin:
    Skien
    did:
    2328082
    destination:
    Eikefet
  41. oid:
    2327951
    origin:
    Skien
    did:
    2327917
    destination:
    Kambo
  42. oid:
    2327951
    origin:
    Skien
    did:
    2328018
    destination:
    Hausvikstrand
  43. oid:
    2327951
    origin:
    Skien
    did:
    2341694
    destination:
    Voll - Skien
  44. oid:
    2327951
    origin:
    Skien
    did:
    2329112
    destination:
    Skagen
  45. oid:
    2327951
    origin:
    Skien
    did:
    2329112
    destination:
    Skagen
  46. oid:
    2327951
    origin:
    Skien
    did:
    2327955
    destination:
    Herøya
  47. oid:
    2327951
    origin:
    Skien
    did:
    2327969
    destination:
    Valberg - Kragerø
  48. oid:
    2327951
    origin:
    Skien
    did:
    2327996
    destination:
    Kvinesdal
  49. oid:
    2327951
    origin:
    Skien
    did:
    2327939
    destination:
    Moss Nord
  50. oid:
    2327951
    origin:
    Skien
    did:
    2328012
    destination:
    Rekefjord
  51. oid:
    2327951
    origin:
    Skien
    did:
    2328012
    destination:
    Rekefjord
  52. oid:
    2327951
    origin:
    Skien
    did:
    2327974
    destination:
    Frierfjorden ankring
  53. oid:
    2327951
    origin:
    Skien
    did:
    2327948
    destination:
    Larvik
  54. oid:
    2327951
    origin:
    Skien
    did:
    2447768
    destination:
    Forsand
  55. oid:
    2327951
    origin:
    Skien
    did:
    2328628
    destination:
    Hamburg
  56. oid:
    2327951
    origin:
    Skien
    did:
    2327923
    destination:
    Oslo
  57. oid:
    2327951
    origin:
    Skien
    did:
    2467310
    destination:
    Rottfjorden 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.