Allemannsdata
Manual search

Port-jérôme

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T05:28:50Z.

Havn

havn_id:
2331617
navn:
Port-jérôme
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

26 results

  1. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2327955
    destination:
    Herøya
  2. oid:
    2328216
    origin:
    Steinkjer
    did:
    2331617
    destination:
    Port-jérôme
  3. oid:
    2451822
    origin:
    Gismarvik
    did:
    2331617
    destination:
    Port-jérôme
  4. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2328146
    destination:
    Gunhildvågen
  5. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2327957
    destination:
    Rønningen
  6. oid:
    2328034
    origin:
    Kårstø
    did:
    2331617
    destination:
    Port-jérôme
  7. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2331617
    destination:
    Port-jérôme
  8. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2328123
    destination:
    Fonnesflaket ankring
  9. oid:
    2328099
    origin:
    Mongstad
    did:
    2331617
    destination:
    Port-jérôme
  10. oid:
    2328099
    origin:
    Mongstad
    did:
    2331617
    destination:
    Port-jérôme
  11. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2454528
    destination:
    Skålevik
  12. oid:
    2328099
    origin:
    Mongstad
    did:
    2331617
    destination:
    Port-jérôme
  13. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2328123
    destination:
    Fonnesflaket ankring
  14. oid:
    2328099
    origin:
    Mongstad
    did:
    2331617
    destination:
    Port-jérôme
  15. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2328099
    destination:
    Mongstad
  16. oid:
    2328034
    origin:
    Kårstø
    did:
    2331617
    destination:
    Port-jérôme
  17. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2328034
    destination:
    Kårstø
  18. oid:
    2328034
    origin:
    Kårstø
    did:
    2331617
    destination:
    Port-jérôme
  19. oid:
    2328034
    origin:
    Kårstø
    did:
    2331617
    destination:
    Port-jérôme
  20. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2454528
    destination:
    Skålevik
  21. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2454528
    destination:
    Skålevik
  22. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2353289
    destination:
    Vikan - Bodø
  23. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2447632
    destination:
    Slagentangen ankring
  24. oid:
    2327927
    origin:
    Slagentangen
    did:
    2331617
    destination:
    Port-jérôme
  25. oid:
    2327927
    origin:
    Slagentangen
    did:
    2331617
    destination:
    Port-jérôme
  26. oid:
    2331617
    origin:
    Port-jérôme
    did:
    2447632
    destination:
    Slagentangen 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.

AI agent? Read the complete navigation and programming guide.