Jørpeland

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:49:43Z.

Havn

havn_id:
2328032
navn:
Jørpeland
kode:
NOJLD
type:
Havn
kommune:
Strand
fylke:
Rogaland
lat:
59.017035
lon:
6.040978

Port-call and departure connections

26 results

  1. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328028
    destination:
    Haugesund
  2. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328102
    destination:
    Norheimsund
  3. oid:
    2447728
    origin:
    Flatøy
    did:
    2328032
    destination:
    Jørpeland
  4. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328032
    destination:
    Jørpeland
  5. oid:
    2328048
    origin:
    Stavanger
    did:
    2328032
    destination:
    Jørpeland
  6. oid:
    2328048
    origin:
    Stavanger
    did:
    2328032
    destination:
    Jørpeland
  7. oid:
    2328048
    origin:
    Stavanger
    did:
    2328032
    destination:
    Jørpeland
  8. oid:
    2328048
    origin:
    Stavanger
    did:
    2328032
    destination:
    Jørpeland
  9. oid:
    2329491
    origin:
    Lerwick
    did:
    2328032
    destination:
    Jørpeland
  10. oid:
    2328103
    origin:
    Odda
    did:
    2328032
    destination:
    Jørpeland
  11. oid:
    2328022
    origin:
    Dirdal
    did:
    2328032
    destination:
    Jørpeland
  12. oid:
    2328045
    origin:
    Skudeneshavn
    did:
    2328032
    destination:
    Jørpeland
  13. oid:
    2328045
    origin:
    Skudeneshavn
    did:
    2328032
    destination:
    Jørpeland
  14. oid:
    2328028
    origin:
    Haugesund
    did:
    2328032
    destination:
    Jørpeland
  15. oid:
    2330578
    origin:
    Ålborg
    did:
    2328032
    destination:
    Jørpeland
  16. oid:
    2328032
    origin:
    Jørpeland
    did:
    2447660
    destination:
    Nordsjøen
  17. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328042
    destination:
    Sandnes
  18. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328042
    destination:
    Sandnes
  19. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328042
    destination:
    Sandnes
  20. oid:
    2328032
    origin:
    Jørpeland
    did:
    2327991
    destination:
    Flekkefjord
  21. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328048
    destination:
    Stavanger
  22. oid:
    2328032
    origin:
    Jørpeland
    did:
    2328048
    destination:
    Stavanger
  23. oid:
    2328032
    origin:
    Jørpeland
    did:
    2450249
    destination:
    Lysebotn
  24. oid:
    2328032
    origin:
    Jørpeland
    did:
    2450249
    destination:
    Lysebotn
  25. oid:
    2328032
    origin:
    Jørpeland
    did:
    2327990
    destination:
    Farsund
  26. oid:
    2328032
    origin:
    Jørpeland
    did:
    2451857
    destination:
    Nedstrandsfjorden

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.