Pietarsaari (jacobstad)

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T07:19:53Z.

Havn

havn_id:
2331422
navn:
Pietarsaari (jacobstad)
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
63.6833333333333
lon:
22.7833333333333

Port-call and departure connections

13 results

  1. oid:
    2328232
    origin:
    Ålesund
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  2. oid:
    2327989
    origin:
    Eydehavn - Arendal
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  3. oid:
    2327989
    origin:
    Eydehavn - Arendal
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  4. oid:
    2327989
    origin:
    Eydehavn - Arendal
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  5. oid:
    2327955
    origin:
    Herøya
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  6. oid:
    2327955
    origin:
    Herøya
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  7. oid:
    2327998
    origin:
    Mandal
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  8. oid:
    2327958
    origin:
    Rafnes
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  9. oid:
    2327904
    origin:
    Drammen
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  10. oid:
    2327904
    origin:
    Drammen
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  11. oid:
    2327904
    origin:
    Drammen
    did:
    2331422
    destination:
    Pietarsaari (jacobstad)
  12. oid:
    2331422
    origin:
    Pietarsaari (jacobstad)
    did:
    2452139
    destination:
    Skjærhalden
  13. oid:
    2331422
    origin:
    Pietarsaari (jacobstad)
    did:
    2327974
    destination:
    Frierfjorden ankring

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.