Middlesborough

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T05:31:14Z.

Havn

havn_id:
2329521
navn:
Middlesborough
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

32 results

  1. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327926
    destination:
    Sarpsborg
  2. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328012
    destination:
    Rekefjord
  3. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328012
    destination:
    Rekefjord
  4. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328122
    destination:
    Tyssedal
  5. oid:
    2328103
    origin:
    Odda
    did:
    2329521
    destination:
    Middlesborough
  6. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  7. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327998
    destination:
    Mandal
  8. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  9. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  10. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328125
    destination:
    Sløvåg Industriområde
  11. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  12. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  13. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327955
    destination:
    Herøya
  14. oid:
    2329521
    origin:
    Middlesborough
    did:
    2450243
    destination:
    Høylandsbygda
  15. oid:
    2452198
    origin:
    Bøvågen - Karmøy
    did:
    2329521
    destination:
    Middlesborough
  16. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328123
    destination:
    Fonnesflaket ankring
  17. oid:
    2328122
    origin:
    Tyssedal
    did:
    2329521
    destination:
    Middlesborough
  18. oid:
    2328122
    origin:
    Tyssedal
    did:
    2329521
    destination:
    Middlesborough
  19. oid:
    2328122
    origin:
    Tyssedal
    did:
    2329521
    destination:
    Middlesborough
  20. oid:
    2341458
    origin:
    Leirvik
    did:
    2329521
    destination:
    Middlesborough
  21. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329521
    destination:
    Middlesborough
  22. oid:
    2329521
    origin:
    Middlesborough
    did:
    2451550
    destination:
    Stord base
  23. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327998
    destination:
    Mandal
  24. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327955
    destination:
    Herøya
  25. oid:
    2328012
    origin:
    Rekefjord
    did:
    2329521
    destination:
    Middlesborough
  26. oid:
    2328122
    origin:
    Tyssedal
    did:
    2329521
    destination:
    Middlesborough
  27. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327955
    destination:
    Herøya
  28. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327974
    destination:
    Frierfjorden ankring
  29. oid:
    2329521
    origin:
    Middlesborough
    did:
    2327955
    destination:
    Herøya
  30. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328122
    destination:
    Tyssedal
  31. oid:
    2329521
    origin:
    Middlesborough
    did:
    2328012
    destination:
    Rekefjord
  32. oid:
    2341605
    origin:
    Søvik
    did:
    2329521
    destination:
    Middlesborough

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.