Lysebotn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T20:39:24Z.

Havn

havn_id:
2450249
navn:
Lysebotn
kode:
NOLYF
type:
Havn
kommune:
Sandnes
fylke:
Rogaland
lat:
59.05469
lon:
6.64527

Port-call and departure connections

34 results

  1. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328042
    destination:
    Sandnes
  2. oid:
    2328042
    origin:
    Sandnes
    did:
    2450249
    destination:
    Lysebotn
  3. oid:
    2450249
    origin:
    Lysebotn
    did:
    2447381
    destination:
    Vats
  4. oid:
    2328106
    origin:
    Rosendal
    did:
    2450249
    destination:
    Lysebotn
  5. oid:
    2450249
    origin:
    Lysebotn
    did:
    2464183
    destination:
    Lauvvik ferjekai
  6. oid:
    2450249
    origin:
    Lysebotn
    did:
    2457265
    destination:
    Lauvvika
  7. oid:
    2464183
    origin:
    Lauvvik ferjekai
    did:
    2450249
    destination:
    Lysebotn
  8. oid:
    2450249
    origin:
    Lysebotn
    did:
    2464183
    destination:
    Lauvvik ferjekai
  9. oid:
    2466657
    origin:
    Lauvvik hurtigbåtkai
    did:
    2450249
    destination:
    Lysebotn
  10. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328048
    destination:
    Stavanger
  11. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328048
    destination:
    Stavanger
  12. oid:
    2328045
    origin:
    Skudeneshavn
    did:
    2450249
    destination:
    Lysebotn
  13. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328078
    destination:
    Bergen
  14. oid:
    2328048
    origin:
    Stavanger
    did:
    2450249
    destination:
    Lysebotn
  15. oid:
    2328042
    origin:
    Sandnes
    did:
    2450249
    destination:
    Lysebotn
  16. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328032
    destination:
    Jørpeland
  17. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328042
    destination:
    Sandnes
  18. oid:
    2328032
    origin:
    Jørpeland
    did:
    2450249
    destination:
    Lysebotn
  19. oid:
    2450249
    origin:
    Lysebotn
    did:
    2467309
    destination:
    Riskafjorden ankring
  20. oid:
    2328048
    origin:
    Stavanger
    did:
    2450249
    destination:
    Lysebotn
  21. oid:
    2450249
    origin:
    Lysebotn
    did:
    2447637
    destination:
    Steinvig
  22. oid:
    2328048
    origin:
    Stavanger
    did:
    2450249
    destination:
    Lysebotn
  23. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328048
    destination:
    Stavanger
  24. oid:
    2327923
    origin:
    Oslo
    did:
    2450249
    destination:
    Lysebotn
  25. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328045
    destination:
    Skudeneshavn
  26. oid:
    2328048
    origin:
    Stavanger
    did:
    2450249
    destination:
    Lysebotn
  27. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328035
    destination:
    Lysefjorden
  28. oid:
    2328032
    origin:
    Jørpeland
    did:
    2450249
    destination:
    Lysebotn
  29. oid:
    2450249
    origin:
    Lysebotn
    did:
    2328048
    destination:
    Stavanger
  30. oid:
    2447768
    origin:
    Forsand
    did:
    2450249
    destination:
    Lysebotn
  31. oid:
    2450249
    origin:
    Lysebotn
    did:
    2457265
    destination:
    Lauvvika
  32. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450249
    destination:
    Lysebotn
  33. oid:
    2450249
    origin:
    Lysebotn
    did:
    2451493
    destination:
    Mastrafjorden
  34. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450249
    destination:
    Lysebotn

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.