Naantali (nådendal)

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T11:51:03Z.

Havn

havn_id:: 2331416
navn:: Naantali (nådendal)
kode:: not reported by source
type:: Havn
kommune:: not reported by source
fylke:: not reported by source
lat:: 60.45
lon:: 22.0333333333333

Port-call and departure connections

9 results

oid:
2331416
origin:
Naantali (nådendal)
did:
2328099
destination:
Mongstad
oid:
2331416
origin:
Naantali (nådendal)
did:
2327955
destination:
Herøya
oid:
2331416
origin:
Naantali (nådendal)
did:
2328050
destination:
Tau
oid:
2331416
origin:
Naantali (nådendal)
did:
2328050
destination:
Tau
oid:
2331416
origin:
Naantali (nådendal)
did:
2328050
destination:
Tau
oid:
2331416
origin:
Naantali (nådendal)
did:
2328050
destination:
Tau
oid:
2331416
origin:
Naantali (nådendal)
did:
2327939
destination:
Moss Nord
oid:
2327923
origin:
Oslo
did:
2331416
destination:
Naantali (nådendal)
oid:
2327908
origin:
Fredrikstad
did:
2331416
destination:
Naantali (nådendal)

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.