Valhall

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-05T02:12:02Z.

Havn

havn_id:
2456565
navn:
Valhall
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

55 results

  1. oid:
    2456565
    origin:
    Valhall
    did:
    2328048
    destination:
    Stavanger
  2. oid:
    2328048
    origin:
    Stavanger
    did:
    2456565
    destination:
    Valhall
  3. oid:
    2456565
    origin:
    Valhall
    did:
    2328023
    destination:
    Dusavik
  4. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2456565
    destination:
    Valhall
  5. oid:
    2328084
    origin:
    Florø
    did:
    2456565
    destination:
    Valhall
  6. oid:
    2456565
    origin:
    Valhall
    did:
    2447404
    destination:
    Storesund
  7. oid:
    2447404
    origin:
    Storesund
    did:
    2456565
    destination:
    Valhall
  8. oid:
    2328049
    origin:
    Tananger
    did:
    2456565
    destination:
    Valhall
  9. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  10. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  11. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  12. oid:
    2456565
    origin:
    Valhall
    did:
    2328061
    destination:
    Mekjarvik
  13. oid:
    2328049
    origin:
    Tananger
    did:
    2456565
    destination:
    Valhall
  14. oid:
    2328048
    origin:
    Stavanger
    did:
    2456565
    destination:
    Valhall
  15. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  16. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  17. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  18. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  19. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  20. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  21. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  22. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  23. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  24. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  25. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  26. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  27. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  28. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  29. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  30. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  31. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  32. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  33. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  34. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  35. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  36. oid:
    2328049
    origin:
    Tananger
    did:
    2456565
    destination:
    Valhall
  37. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  38. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  39. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  40. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  41. oid:
    2327988
    origin:
    Egersund
    did:
    2456565
    destination:
    Valhall
  42. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  43. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  44. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  45. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  46. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  47. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  48. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  49. oid:
    2456565
    origin:
    Valhall
    did:
    2447455
    destination:
    Risavika
  50. oid:
    2447455
    origin:
    Risavika
    did:
    2456565
    destination:
    Valhall
  51. oid:
    2456565
    origin:
    Valhall
    did:
    2328061
    destination:
    Mekjarvik
  52. oid:
    2328042
    origin:
    Sandnes
    did:
    2456565
    destination:
    Valhall
  53. oid:
    2451822
    origin:
    Gismarvik
    did:
    2456565
    destination:
    Valhall
  54. oid:
    2328048
    origin:
    Stavanger
    did:
    2456565
    destination:
    Valhall
  55. oid:
    2456565
    origin:
    Valhall
    did:
    2328028
    destination:
    Haugesund

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.