Greenock

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:07:27Z.

Havn

havn_id:
2329420
navn:
Greenock
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
55.9333333333333
lon:
-4.75

Port-call and departure connections

52 results

  1. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  2. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  3. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  4. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  5. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  6. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  7. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  8. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  9. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  10. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  11. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  12. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  13. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  14. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  15. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  16. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  17. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  18. oid:
    2329277
    origin:
    Belfast
    did:
    2329420
    destination:
    Greenock
  19. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  20. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  21. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  22. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  23. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  24. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  25. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  26. oid:
    2328212
    origin:
    Skogn
    did:
    2329420
    destination:
    Greenock
  27. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  28. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  29. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  30. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  31. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  32. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  33. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  34. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  35. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  36. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  37. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  38. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  39. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  40. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  41. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  42. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  43. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  44. oid:
    2329420
    origin:
    Greenock
    did:
    2328212
    destination:
    Skogn
  45. oid:
    2329420
    origin:
    Greenock
    did:
    2330850
    destination:
    Belfast
  46. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  47. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  48. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  49. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  50. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  51. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast
  52. oid:
    2329420
    origin:
    Greenock
    did:
    2329277
    destination:
    Belfast

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.