Asnæsværkets Havn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T04:42:50Z.

Havn

havn_id:: 2329000
navn:: Asnæsværkets Havn
kode:: not reported by source
type:: Havn
kommune:: not reported by source
fylke:: not reported by source
lat:: 55.6593132
lon:: 11.079444

Port-call and departure connections

8 results

oid:
2329000
origin:
Asnæsværkets Havn
did:
2327904
destination:
Drammen
oid:
2329000
origin:
Asnæsværkets Havn
did:
2328056
destination:
Jelsa
oid:
2328099
origin:
Mongstad
did:
2329000
destination:
Asnæsværkets Havn
oid:
2447388
origin:
Haugsøytangen ankring
did:
2329000
destination:
Asnæsværkets Havn
oid:
2329000
origin:
Asnæsværkets Havn
did:
2327989
destination:
Eydehavn - Arendal
oid:
2329000
origin:
Asnæsværkets Havn
did:
2327989
destination:
Eydehavn - Arendal
oid:
2329000
origin:
Asnæsværkets Havn
did:
2328069
destination:
Breiviga
oid:
2329000
origin:
Asnæsværkets Havn
did:
2328069
destination:
Breiviga

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.