Thorshofn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T18:13:21Z.

Havn

havn_id:
2329860
navn:
Thorshofn
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
66.1990802
lon:
-15.3372652

Port-call and departure connections

32 results

  1. oid:
    2329860
    origin:
    Thorshofn
    did:
    2447404
    destination:
    Storesund
  2. oid:
    2329797
    origin:
    Akureyri
    did:
    2329860
    destination:
    Thorshofn
  3. oid:
    2329860
    origin:
    Thorshofn
    did:
    2329812
    destination:
    Faskrudsfjørdur
  4. oid:
    2329827
    origin:
    Isafjørdur - Høfn
    did:
    2329860
    destination:
    Thorshofn
  5. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328063
    destination:
    Husøy - Karmøy
  6. oid:
    2329820
    origin:
    Hofn, Hornafjørdur
    did:
    2329860
    destination:
    Thorshofn
  7. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328063
    destination:
    Husøy - Karmøy
  8. oid:
    2447404
    origin:
    Storesund
    did:
    2329860
    destination:
    Thorshofn
  9. oid:
    2329860
    origin:
    Thorshofn
    did:
    2330484
    destination:
    Stettin
  10. oid:
    2329862
    origin:
    Vopnafjørdur
    did:
    2329860
    destination:
    Thorshofn
  11. oid:
    2447404
    origin:
    Storesund
    did:
    2329860
    destination:
    Thorshofn
  12. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328063
    destination:
    Husøy - Karmøy
  13. oid:
    2329860
    origin:
    Thorshofn
    did:
    2447404
    destination:
    Storesund
  14. oid:
    2329862
    origin:
    Vopnafjørdur
    did:
    2329860
    destination:
    Thorshofn
  15. oid:
    2329860
    origin:
    Thorshofn
    did:
    2330483
    destination:
    Klaipeda
  16. oid:
    2329860
    origin:
    Thorshofn
    did:
    2329862
    destination:
    Vopnafjørdur
  17. oid:
    2458377
    origin:
    Tórshavn
    did:
    2329860
    destination:
    Thorshofn
  18. oid:
    2329860
    origin:
    Thorshofn
    did:
    2329862
    destination:
    Vopnafjørdur
  19. oid:
    2329849
    origin:
    Siglufjørdur - Høfn
    did:
    2329860
    destination:
    Thorshofn
  20. oid:
    2329860
    origin:
    Thorshofn
    did:
    2329862
    destination:
    Vopnafjørdur
  21. oid:
    2447404
    origin:
    Storesund
    did:
    2329860
    destination:
    Thorshofn
  22. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328063
    destination:
    Husøy - Karmøy
  23. oid:
    2329860
    origin:
    Thorshofn
    did:
    2329024
    destination:
    Frederikshavn
  24. oid:
    2329859
    origin:
    Thorlakshofn
    did:
    2329860
    destination:
    Thorshofn
  25. oid:
    2328232
    origin:
    Ålesund
    did:
    2329860
    destination:
    Thorshofn
  26. oid:
    2328100
    origin:
    Måløy
    did:
    2329860
    destination:
    Thorshofn
  27. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328100
    destination:
    Måløy
  28. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328157
    destination:
    Averøy
  29. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2329860
    destination:
    Thorshofn
  30. oid:
    2329860
    origin:
    Thorshofn
    did:
    2328125
    destination:
    Sløvåg Industriområde
  31. oid:
    2329843
    origin:
    Reydarfjørdur
    did:
    2329860
    destination:
    Thorshofn
  32. oid:
    2447404
    origin:
    Storesund
    did:
    2329860
    destination:
    Thorshofn

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.