Blyth

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-05T01:32:21Z.

Havn

havn_id:
2329294
navn:
Blyth
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
55.126957
lon:
-1.510277

Port-call and departure connections

35 results

  1. oid:
    2329294
    origin:
    Blyth
    did:
    2328012
    destination:
    Rekefjord
  2. oid:
    2328234
    origin:
    Valsneset
    did:
    2329294
    destination:
    Blyth
  3. oid:
    2329294
    origin:
    Blyth
    did:
    2451460
    destination:
    Jøssingfjord
  4. oid:
    2329294
    origin:
    Blyth
    did:
    2328063
    destination:
    Husøy - Karmøy
  5. oid:
    2329294
    origin:
    Blyth
    did:
    2328063
    destination:
    Husøy - Karmøy
  6. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2329294
    destination:
    Blyth
  7. oid:
    2329294
    origin:
    Blyth
    did:
    2328033
    destination:
    Kopervik
  8. oid:
    2454918
    origin:
    Grane
    did:
    2329294
    destination:
    Blyth
  9. oid:
    2328224
    origin:
    Ulsteinvik
    did:
    2329294
    destination:
    Blyth
  10. oid:
    2329294
    origin:
    Blyth
    did:
    2329253
    destination:
    Aberdeen
  11. oid:
    2330477
    origin:
    Rotterdam
    did:
    2329294
    destination:
    Blyth
  12. oid:
    2328231
    origin:
    Åheim
    did:
    2329294
    destination:
    Blyth
  13. oid:
    2329294
    origin:
    Blyth
    did:
    2328082
    destination:
    Eikefet
  14. oid:
    2329294
    origin:
    Blyth
    did:
    2328129
    destination:
    Ågotnes
  15. oid:
    2328170
    origin:
    Fiskarstrand
    did:
    2329294
    destination:
    Blyth
  16. oid:
    2328113
    origin:
    Bjørnafjorden
    did:
    2329294
    destination:
    Blyth
  17. oid:
    2328227
    origin:
    Verdal
    did:
    2329294
    destination:
    Blyth
  18. oid:
    2329294
    origin:
    Blyth
    did:
    2451550
    destination:
    Stord base
  19. oid:
    2329294
    origin:
    Blyth
    did:
    2456966
    destination:
    Steinsvika - Volda
  20. oid:
    2329294
    origin:
    Blyth
    did:
    2328028
    destination:
    Haugesund
  21. oid:
    2328028
    origin:
    Haugesund
    did:
    2329294
    destination:
    Blyth
  22. oid:
    2329294
    origin:
    Blyth
    did:
    2328028
    destination:
    Haugesund
  23. oid:
    2329294
    origin:
    Blyth
    did:
    2328042
    destination:
    Sandnes
  24. oid:
    2329294
    origin:
    Blyth
    did:
    2341443
    destination:
    Kvitsøy
  25. oid:
    2329294
    origin:
    Blyth
    did:
    2450231
    destination:
    Eikelandsosen
  26. oid:
    2328078
    origin:
    Bergen
    did:
    2329294
    destination:
    Blyth
  27. oid:
    2329294
    origin:
    Blyth
    did:
    2328189
    destination:
    Kristiansund
  28. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2329294
    destination:
    Blyth
  29. oid:
    2329294
    origin:
    Blyth
    did:
    2328048
    destination:
    Stavanger
  30. oid:
    2329294
    origin:
    Blyth
    did:
    2327974
    destination:
    Frierfjorden ankring
  31. oid:
    2447455
    origin:
    Risavika
    did:
    2329294
    destination:
    Blyth
  32. oid:
    2329294
    origin:
    Blyth
    did:
    2328061
    destination:
    Mekjarvik
  33. oid:
    2328160
    origin:
    Brattvåg
    did:
    2329294
    destination:
    Blyth
  34. oid:
    2329294
    origin:
    Blyth
    did:
    2328048
    destination:
    Stavanger
  35. oid:
    2329294
    origin:
    Blyth
    did:
    2328048
    destination:
    Stavanger

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.