Goole

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T08:45:07Z.

Havn

havn_id:
2329416
navn:
Goole
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
53.7166666666667
lon:
-0.866666666666667

Port-call and departure connections

47 results

  1. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  2. oid:
    2447653
    origin:
    Skarholmen
    did:
    2329416
    destination:
    Goole
  3. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  4. oid:
    2328100
    origin:
    Måløy
    did:
    2329416
    destination:
    Goole
  5. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  6. oid:
    2328100
    origin:
    Måløy
    did:
    2329416
    destination:
    Goole
  7. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  8. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  9. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  10. oid:
    2328223
    origin:
    Trondheim
    did:
    2329416
    destination:
    Goole
  11. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  12. oid:
    2329416
    origin:
    Goole
    did:
    2327904
    destination:
    Drammen
  13. oid:
    2329416
    origin:
    Goole
    did:
    2328010
    destination:
    Maurholen
  14. oid:
    2327994
    origin:
    Høllen
    did:
    2329416
    destination:
    Goole
  15. oid:
    2329416
    origin:
    Goole
    did:
    2447401
    destination:
    Bøneset - Karmøy
  16. oid:
    2327943
    origin:
    Brevik
    did:
    2329416
    destination:
    Goole
  17. oid:
    2329416
    origin:
    Goole
    did:
    2328010
    destination:
    Maurholen
  18. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  19. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  20. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  21. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  22. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  23. oid:
    2329416
    origin:
    Goole
    did:
    2451460
    destination:
    Jøssingfjord
  24. oid:
    2329416
    origin:
    Goole
    did:
    2451460
    destination:
    Jøssingfjord
  25. oid:
    2329416
    origin:
    Goole
    did:
    2328018
    destination:
    Hausvikstrand
  26. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  27. oid:
    2329416
    origin:
    Goole
    did:
    2328012
    destination:
    Rekefjord
  28. oid:
    2329416
    origin:
    Goole
    did:
    2328124
    destination:
    Mongstadbase
  29. oid:
    2329416
    origin:
    Goole
    did:
    2328189
    destination:
    Kristiansund
  30. oid:
    2328023
    origin:
    Dusavik
    did:
    2329416
    destination:
    Goole
  31. oid:
    2329416
    origin:
    Goole
    did:
    2328010
    destination:
    Maurholen
  32. oid:
    2329416
    origin:
    Goole
    did:
    2450230
    destination:
    Eidsnes
  33. oid:
    2329820
    origin:
    Hofn, Hornafjørdur
    did:
    2329416
    destination:
    Goole
  34. oid:
    2327943
    origin:
    Brevik
    did:
    2329416
    destination:
    Goole
  35. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2329416
    destination:
    Goole
  36. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2329416
    destination:
    Goole
  37. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  38. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329416
    destination:
    Goole
  39. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole
  40. oid:
    2329416
    origin:
    Goole
    did:
    2328165
    destination:
    Eide
  41. oid:
    2329416
    origin:
    Goole
    did:
    2328099
    destination:
    Mongstad
  42. oid:
    2329416
    origin:
    Goole
    did:
    2451460
    destination:
    Jøssingfjord
  43. oid:
    2450271
    origin:
    Torangsvåg
    did:
    2329416
    destination:
    Goole
  44. oid:
    2329416
    origin:
    Goole
    did:
    2328100
    destination:
    Måløy
  45. oid:
    2329416
    origin:
    Goole
    did:
    2327998
    destination:
    Mandal
  46. oid:
    2329416
    origin:
    Goole
    did:
    2328069
    destination:
    Breiviga
  47. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329416
    destination:
    Goole

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.