Bekkeri

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-11T09:32:09Z.

Havn

havn_id:
2334807
navn:
Bekkeri
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

10 results

  1. oid:
    2334807
    origin:
    Bekkeri
    did:
    2334828
    destination:
    Paljassaare
  2. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2334807
    destination:
    Bekkeri
  3. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2334807
    destination:
    Bekkeri
  4. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  5. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  6. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  7. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  8. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  9. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri
  10. oid:
    2328069
    origin:
    Breiviga
    did:
    2334807
    destination:
    Bekkeri

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.