Alvheim

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T10:27:14Z.

Havn

havn_id:
2456513
navn:
Alvheim
kode:
not reported by source
type:
Offshoreinstallasjon
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

30 results

  1. oid:
    2447455
    origin:
    Risavika
    did:
    2456513
    destination:
    Alvheim
  2. oid:
    2328048
    origin:
    Stavanger
    did:
    2456513
    destination:
    Alvheim
  3. oid:
    2456513
    origin:
    Alvheim
    did:
    2328048
    destination:
    Stavanger
  4. oid:
    2328049
    origin:
    Tananger
    did:
    2456513
    destination:
    Alvheim
  5. oid:
    2456513
    origin:
    Alvheim
    did:
    2447455
    destination:
    Risavika
  6. oid:
    2328048
    origin:
    Stavanger
    did:
    2456513
    destination:
    Alvheim
  7. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2456513
    destination:
    Alvheim
  8. oid:
    2456513
    origin:
    Alvheim
    did:
    2328051
    destination:
    Åmøyfjorden ankring
  9. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  10. oid:
    2456513
    origin:
    Alvheim
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  11. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  12. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  13. oid:
    2456513
    origin:
    Alvheim
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  14. oid:
    2328099
    origin:
    Mongstad
    did:
    2456513
    destination:
    Alvheim
  15. oid:
    2456513
    origin:
    Alvheim
    did:
    2328099
    destination:
    Mongstad
  16. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  17. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  18. oid:
    2456513
    origin:
    Alvheim
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  19. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  20. oid:
    2328099
    origin:
    Mongstad
    did:
    2456513
    destination:
    Alvheim
  21. oid:
    2456513
    origin:
    Alvheim
    did:
    2328099
    destination:
    Mongstad
  22. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  23. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  24. oid:
    2456513
    origin:
    Alvheim
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  25. oid:
    2456513
    origin:
    Alvheim
    did:
    2328099
    destination:
    Mongstad
  26. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  27. oid:
    2456513
    origin:
    Alvheim
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  28. oid:
    2456513
    origin:
    Alvheim
    did:
    2328099
    destination:
    Mongstad
  29. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim
  30. oid:
    2451779
    origin:
    Karlsmedgrunnen ankring
    did:
    2456513
    destination:
    Alvheim

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.