Lauvvika

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:57:33Z.

Havn

havn_id:
2457265
navn:
Lauvvika
kode:
NOSAS
type:
Havn
kommune:
Sandnes
fylke:
Rogaland
lat:
58.89415
lon:
6.056167

Port-call and departure connections

35 results

  1. oid:
    2451857
    origin:
    Nedstrandsfjorden
    did:
    2457265
    destination:
    Lauvvika
  2. oid:
    2462564
    origin:
    Skjellanger
    did:
    2457265
    destination:
    Lauvvika
  3. oid:
    2460981
    origin:
    Espevær
    did:
    2457265
    destination:
    Lauvvika
  4. oid:
    2328048
    origin:
    Stavanger
    did:
    2457265
    destination:
    Lauvvika
  5. oid:
    2328048
    origin:
    Stavanger
    did:
    2457265
    destination:
    Lauvvika
  6. oid:
    2328048
    origin:
    Stavanger
    did:
    2457265
    destination:
    Lauvvika
  7. oid:
    2328070
    origin:
    Fiskå - Strand
    did:
    2457265
    destination:
    Lauvvika
  8. oid:
    2447385
    origin:
    Skogsvåg
    did:
    2457265
    destination:
    Lauvvika
  9. oid:
    2451494
    origin:
    Stavanger Øst
    did:
    2457265
    destination:
    Lauvvika
  10. oid:
    2328033
    origin:
    Kopervik
    did:
    2457265
    destination:
    Lauvvika
  11. oid:
    2328033
    origin:
    Kopervik
    did:
    2457265
    destination:
    Lauvvika
  12. oid:
    2447669
    origin:
    Boknafjorden
    did:
    2457265
    destination:
    Lauvvika
  13. oid:
    2447669
    origin:
    Boknafjorden
    did:
    2457265
    destination:
    Lauvvika
  14. oid:
    2447669
    origin:
    Boknafjorden
    did:
    2457265
    destination:
    Lauvvika
  15. oid:
    2447669
    origin:
    Boknafjorden
    did:
    2457265
    destination:
    Lauvvika
  16. oid:
    2447404
    origin:
    Storesund
    did:
    2457265
    destination:
    Lauvvika
  17. oid:
    2451767
    origin:
    Sandeid
    did:
    2457265
    destination:
    Lauvvika
  18. oid:
    2466200
    origin:
    Nedrevågen
    did:
    2457265
    destination:
    Lauvvika
  19. oid:
    2457265
    origin:
    Lauvvika
    did:
    2328028
    destination:
    Haugesund
  20. oid:
    2457265
    origin:
    Lauvvika
    did:
    2328028
    destination:
    Haugesund
  21. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450267
    destination:
    Sunde
  22. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450267
    destination:
    Sunde
  23. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450267
    destination:
    Sunde
  24. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450267
    destination:
    Sunde
  25. oid:
    2457265
    origin:
    Lauvvika
    did:
    2447404
    destination:
    Storesund
  26. oid:
    2457265
    origin:
    Lauvvika
    did:
    2447669
    destination:
    Boknafjorden
  27. oid:
    2457265
    origin:
    Lauvvika
    did:
    2447669
    destination:
    Boknafjorden
  28. oid:
    2457265
    origin:
    Lauvvika
    did:
    2447669
    destination:
    Boknafjorden
  29. oid:
    2457265
    origin:
    Lauvvika
    did:
    2458772
    destination:
    Føresvik - Bokn
  30. oid:
    2457265
    origin:
    Lauvvika
    did:
    2451494
    destination:
    Stavanger Øst
  31. oid:
    2457265
    origin:
    Lauvvika
    did:
    2328048
    destination:
    Stavanger
  32. oid:
    2457265
    origin:
    Lauvvika
    did:
    2328048
    destination:
    Stavanger
  33. oid:
    2457265
    origin:
    Lauvvika
    did:
    2450249
    destination:
    Lysebotn
  34. oid:
    2457265
    origin:
    Lauvvika
    did:
    2457098
    destination:
    Bekkjarvik
  35. oid:
    2457265
    origin:
    Lauvvika
    did:
    2341292
    destination:
    Bømlo

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.