Vats

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T07:39:06Z.

Havn

havn_id:
2447381
navn:
Vats
kode:
NOVTS
type:
Havn
kommune:
Vindafjord
fylke:
Rogaland
lat:
59.47532
lon:
5.73696

Port-call and departure connections

56 results

  1. oid:
    2447381
    origin:
    Vats
    did:
    2328048
    destination:
    Stavanger
  2. oid:
    2451767
    origin:
    Sandeid
    did:
    2447381
    destination:
    Vats
  3. oid:
    2447381
    origin:
    Vats
    did:
    2328050
    destination:
    Tau
  4. oid:
    2451826
    origin:
    Årdal - Hjelmeland
    did:
    2447381
    destination:
    Vats
  5. oid:
    2447381
    origin:
    Vats
    did:
    2328069
    destination:
    Breiviga
  6. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2447381
    destination:
    Vats
  7. oid:
    2447381
    origin:
    Vats
    did:
    2328054
    destination:
    Helle - Forsand
  8. oid:
    2447404
    origin:
    Storesund
    did:
    2447381
    destination:
    Vats
  9. oid:
    2447381
    origin:
    Vats
    did:
    2330484
    destination:
    Stettin
  10. oid:
    2328025
    origin:
    Forus
    did:
    2447381
    destination:
    Vats
  11. oid:
    2447381
    origin:
    Vats
    did:
    2447404
    destination:
    Storesund
  12. oid:
    2328091
    origin:
    Høyanger
    did:
    2447381
    destination:
    Vats
  13. oid:
    2447381
    origin:
    Vats
    did:
    2447768
    destination:
    Forsand
  14. oid:
    2328022
    origin:
    Dirdal
    did:
    2447381
    destination:
    Vats
  15. oid:
    2447381
    origin:
    Vats
    did:
    2327988
    destination:
    Egersund
  16. oid:
    2452138
    origin:
    Vikedal
    did:
    2447381
    destination:
    Vats
  17. oid:
    2447381
    origin:
    Vats
    did:
    2327988
    destination:
    Egersund
  18. oid:
    2328043
    origin:
    Sauda
    did:
    2447381
    destination:
    Vats
  19. oid:
    2447381
    origin:
    Vats
    did:
    2328056
    destination:
    Jelsa
  20. oid:
    2447404
    origin:
    Storesund
    did:
    2447381
    destination:
    Vats
  21. oid:
    2328028
    origin:
    Haugesund
    did:
    2447381
    destination:
    Vats
  22. oid:
    2447381
    origin:
    Vats
    did:
    2328028
    destination:
    Haugesund
  23. oid:
    2328028
    origin:
    Haugesund
    did:
    2447381
    destination:
    Vats
  24. oid:
    2447381
    origin:
    Vats
    did:
    2328064
    destination:
    Ølen
  25. oid:
    2328975
    origin:
    Wismar
    did:
    2447381
    destination:
    Vats
  26. oid:
    2447381
    origin:
    Vats
    did:
    2328975
    destination:
    Wismar
  27. oid:
    2328873
    origin:
    Nordenham
    did:
    2447381
    destination:
    Vats
  28. oid:
    2447381
    origin:
    Vats
    did:
    2328022
    destination:
    Dirdal
  29. oid:
    2452147
    origin:
    Kollsnes Øst
    did:
    2447381
    destination:
    Vats
  30. oid:
    2447381
    origin:
    Vats
    did:
    2447404
    destination:
    Storesund
  31. oid:
    2328048
    origin:
    Stavanger
    did:
    2447381
    destination:
    Vats
  32. oid:
    2447381
    origin:
    Vats
    did:
    2328078
    destination:
    Bergen
  33. oid:
    2328048
    origin:
    Stavanger
    did:
    2447381
    destination:
    Vats
  34. oid:
    2450249
    origin:
    Lysebotn
    did:
    2447381
    destination:
    Vats
  35. oid:
    2447381
    origin:
    Vats
    did:
    2328274
    destination:
    Mo i Rana
  36. oid:
    2330180
    origin:
    Halmstad
    did:
    2447381
    destination:
    Vats
  37. oid:
    2447381
    origin:
    Vats
    did:
    2328274
    destination:
    Mo i Rana
  38. oid:
    2327923
    origin:
    Oslo
    did:
    2447381
    destination:
    Vats
  39. oid:
    2447381
    origin:
    Vats
    did:
    2328274
    destination:
    Mo i Rana
  40. oid:
    2330180
    origin:
    Halmstad
    did:
    2447381
    destination:
    Vats
  41. oid:
    2447381
    origin:
    Vats
    did:
    2328048
    destination:
    Stavanger
  42. oid:
    2447381
    origin:
    Vats
    did:
    2328056
    destination:
    Jelsa
  43. oid:
    2447381
    origin:
    Vats
    did:
    2328048
    destination:
    Stavanger
  44. oid:
    2447381
    origin:
    Vats
    did:
    2447381
    destination:
    Vats
  45. oid:
    2328078
    origin:
    Bergen
    did:
    2447381
    destination:
    Vats
  46. oid:
    2447381
    origin:
    Vats
    did:
    2328034
    destination:
    Kårstø
  47. oid:
    2328028
    origin:
    Haugesund
    did:
    2447381
    destination:
    Vats
  48. oid:
    2447381
    origin:
    Vats
    did:
    2447381
    destination:
    Vats
  49. oid:
    2447381
    origin:
    Vats
    did:
    2447381
    destination:
    Vats
  50. oid:
    2447381
    origin:
    Vats
    did:
    2330477
    destination:
    Rotterdam
  51. oid:
    100122
    origin:
    Offshore
    did:
    2447381
    destination:
    Vats
  52. oid:
    2447381
    origin:
    Vats
    did:
    2447381
    destination:
    Vats
  53. oid:
    2447381
    origin:
    Vats
    did:
    2330477
    destination:
    Rotterdam
  54. oid:
    2447381
    origin:
    Vats
    did:
    2447381
    destination:
    Vats
  55. oid:
    2447381
    origin:
    Vats
    did:
    2328051
    destination:
    Åmøyfjorden ankring
  56. oid:
    2447661
    origin:
    Offshoreinst. Nordsjøen
    did:
    2447381
    destination:
    Vats

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.