Vedavågen

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:46:39Z.

Havn

havn_id:
2447474
navn:
Vedavågen
kode:
NOVMD
type:
Havn
kommune:
Karmøy
fylke:
Rogaland
lat:
59.29709
lon:
5.22901

Port-call and departure connections

35 results

  1. oid:
    2447474
    origin:
    Vedavågen
    did:
    2452206
    destination:
    Nord-Atlanteren
  2. oid:
    2447474
    origin:
    Vedavågen
    did:
    2450219
    destination:
    Vormedal
  3. oid:
    2447474
    origin:
    Vedavågen
    did:
    2450219
    destination:
    Vormedal
  4. oid:
    2447474
    origin:
    Vedavågen
    did:
    2450219
    destination:
    Vormedal
  5. oid:
    2447474
    origin:
    Vedavågen
    did:
    2337318
    destination:
    Nuuk (Godthaab)
  6. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447404
    destination:
    Storesund
  7. oid:
    2447455
    origin:
    Risavika
    did:
    2447474
    destination:
    Vedavågen
  8. oid:
    2451828
    origin:
    Buefjorden
    did:
    2447474
    destination:
    Vedavågen
  9. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2447474
    destination:
    Vedavågen
  10. oid:
    2328121
    origin:
    Mjølkevikvarden
    did:
    2447474
    destination:
    Vedavågen
  11. oid:
    2447660
    origin:
    Nordsjøen
    did:
    2447474
    destination:
    Vedavågen
  12. oid:
    2447660
    origin:
    Nordsjøen
    did:
    2447474
    destination:
    Vedavågen
  13. oid:
    2447660
    origin:
    Nordsjøen
    did:
    2447474
    destination:
    Vedavågen
  14. oid:
    2341306
    origin:
    Dimmelsvik
    did:
    2447474
    destination:
    Vedavågen
  15. oid:
    2451777
    origin:
    Burfjord
    did:
    2447474
    destination:
    Vedavågen
  16. oid:
    2328172
    origin:
    Fosnavåg
    did:
    2447474
    destination:
    Vedavågen
  17. oid:
    2328142
    origin:
    Mølstrevåg
    did:
    2447474
    destination:
    Vedavågen
  18. oid:
    2457653
    origin:
    Maurangerfjorden
    did:
    2447474
    destination:
    Vedavågen
  19. oid:
    2450219
    origin:
    Vormedal
    did:
    2447474
    destination:
    Vedavågen
  20. oid:
    2452206
    origin:
    Nord-Atlanteren
    did:
    2447474
    destination:
    Vedavågen
  21. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  22. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  23. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  24. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  25. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  26. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  27. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447660
    destination:
    Nordsjøen
  28. oid:
    2447474
    origin:
    Vedavågen
    did:
    2329491
    destination:
    Lerwick
  29. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447430
    destination:
    Salthella
  30. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447430
    destination:
    Salthella
  31. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447430
    destination:
    Salthella
  32. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447416
    destination:
    Hanøytangen
  33. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447416
    destination:
    Hanøytangen
  34. oid:
    2447474
    origin:
    Vedavågen
    did:
    2447416
    destination:
    Hanøytangen
  35. oid:
    2447474
    origin:
    Vedavågen
    did:
    2328063
    destination:
    Husøy - Karmøy

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.