Fraserburgh

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T12:24:04Z.

Havn

havn_id:
2329399
navn:
Fraserburgh
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

35 results

  1. oid:
    2328078
    origin:
    Bergen
    did:
    2329399
    destination:
    Fraserburgh
  2. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328048
    destination:
    Stavanger
  3. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  4. oid:
    2328023
    origin:
    Dusavik
    did:
    2329399
    destination:
    Fraserburgh
  5. oid:
    2328232
    origin:
    Ålesund
    did:
    2329399
    destination:
    Fraserburgh
  6. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328172
    destination:
    Fosnavåg
  7. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328168
    destination:
    Ellingsøy
  8. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2329399
    destination:
    Fraserburgh
  9. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328225
    destination:
    Uthaug
  10. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2450238
    destination:
    Harøysundet
  11. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328168
    destination:
    Ellingsøy
  12. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  13. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  14. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  15. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  16. oid:
    2328225
    origin:
    Uthaug
    did:
    2329399
    destination:
    Fraserburgh
  17. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2329399
    destination:
    Fraserburgh
  18. oid:
    2452204
    origin:
    Ukjent lokasjon Norge
    did:
    2329399
    destination:
    Fraserburgh
  19. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328063
    destination:
    Husøy - Karmøy
  20. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328063
    destination:
    Husøy - Karmøy
  21. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  22. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328100
    destination:
    Måløy
  23. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  24. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  25. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328181
    destination:
    Hjørungavåg
  26. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  27. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2329399
    destination:
    Fraserburgh
  28. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328168
    destination:
    Ellingsøy
  29. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328100
    destination:
    Måløy
  30. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  31. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328100
    destination:
    Måløy
  32. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2328045
    destination:
    Skudeneshavn
  33. oid:
    2327988
    origin:
    Egersund
    did:
    2329399
    destination:
    Fraserburgh
  34. oid:
    2329399
    origin:
    Fraserburgh
    did:
    2327988
    destination:
    Egersund
  35. oid:
    2328232
    origin:
    Ålesund
    did:
    2329399
    destination:
    Fraserburgh

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.