Allemannsdata Wiki
Manual search

Clydebank

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:43:10Z.

Havn

Open the place page for this point

havn_id:
2336639
navn:
Clydebank
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
55.9
lon:
-4.4

Port-call and departure connections

49 results

  1. oid:
    2336639
    origin:
    Clydebank
    did:
    2447388
    destination:
    Haugsøytangen ankring
  2. oid:
    2336639
    origin:
    Clydebank
    did:
    2447388
    destination:
    Haugsøytangen ankring
  3. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  4. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  5. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  6. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  7. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  8. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  9. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  10. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  11. oid:
    2336639
    origin:
    Clydebank
    did:
    2328123
    destination:
    Fonnesflaket ankring
  12. oid:
    2336639
    origin:
    Clydebank
    did:
    2328053
    destination:
    Falkeidflæet ankring
  13. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  14. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  15. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  16. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  17. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  18. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  19. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  20. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  21. oid:
    2336639
    origin:
    Clydebank
    did:
    2328099
    destination:
    Mongstad
  22. oid:
    2336639
    origin:
    Clydebank
    did:
    2341458
    destination:
    Leirvik
  23. oid:
    2327988
    origin:
    Egersund
    did:
    2336639
    destination:
    Clydebank
  24. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  25. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  26. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  27. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  28. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  29. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  30. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  31. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  32. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  33. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  34. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  35. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  36. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  37. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  38. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  39. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  40. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  41. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  42. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  43. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  44. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  45. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  46. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  47. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  48. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank
  49. oid:
    2328099
    origin:
    Mongstad
    did:
    2336639
    destination:
    Clydebank

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.

AI agent? Read the complete navigation and programming guide.