Allemannsdata
Manual search

Vierow

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T11:45:16Z.

Havn

havn_id:
2449875
navn:
Vierow
kode:
not reported by source
type:
Havn
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

79 results

  1. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  2. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  3. oid:
    2449875
    origin:
    Vierow
    did:
    2328084
    destination:
    Florø
  4. oid:
    2330267
    origin:
    Norrköping
    did:
    2449875
    destination:
    Vierow
  5. oid:
    2449875
    origin:
    Vierow
    did:
    2328162
    destination:
    Freifjorden ankring
  6. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset
  7. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset
  8. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  9. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  10. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  11. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  12. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  13. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  14. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  15. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  16. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  17. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  18. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  19. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  20. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  21. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  22. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  23. oid:
    2449875
    origin:
    Vierow
    did:
    2327939
    destination:
    Moss Nord
  24. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  25. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  26. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  27. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  28. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  29. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  30. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  31. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  32. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  33. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  34. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  35. oid:
    2327923
    origin:
    Oslo
    did:
    2449875
    destination:
    Vierow
  36. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  37. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset
  38. oid:
    2449875
    origin:
    Vierow
    did:
    2330252
    destination:
    Malmø
  39. oid:
    2328942
    origin:
    Stralsund
    did:
    2449875
    destination:
    Vierow
  40. oid:
    2327914
    origin:
    Horten
    did:
    2449875
    destination:
    Vierow
  41. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset
  42. oid:
    2449875
    origin:
    Vierow
    did:
    2328162
    destination:
    Freifjorden ankring
  43. oid:
    2449875
    origin:
    Vierow
    did:
    2328116
    destination:
    Vaksdal
  44. oid:
    2330316
    origin:
    Sölvesborg
    did:
    2449875
    destination:
    Vierow
  45. oid:
    2449875
    origin:
    Vierow
    did:
    2328116
    destination:
    Vaksdal
  46. oid:
    2452686
    origin:
    Lubmin
    did:
    2449875
    destination:
    Vierow
  47. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  48. oid:
    2327955
    origin:
    Herøya
    did:
    2449875
    destination:
    Vierow
  49. oid:
    2449875
    origin:
    Vierow
    did:
    2327988
    destination:
    Egersund
  50. oid:
    2449875
    origin:
    Vierow
    did:
    2328147
    destination:
    Botnaneset - Flora
  51. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  52. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  53. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  54. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  55. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  56. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  57. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  58. oid:
    2449875
    origin:
    Vierow
    did:
    2328308
    destination:
    Halsa Meløy
  59. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  60. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset
  61. oid:
    2327913
    origin:
    Holmestrand
    did:
    2449875
    destination:
    Vierow
  62. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  63. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  64. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  65. oid:
    2330267
    origin:
    Norrköping
    did:
    2449875
    destination:
    Vierow
  66. oid:
    2449875
    origin:
    Vierow
    did:
    2328169
    destination:
    Elnesvågen
  67. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  68. oid:
    2328369
    origin:
    Bergeneset
    did:
    2449875
    destination:
    Vierow
  69. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  70. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  71. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  72. oid:
    2327955
    origin:
    Herøya
    did:
    2449875
    destination:
    Vierow
  73. oid:
    2449875
    origin:
    Vierow
    did:
    2327951
    destination:
    Skien
  74. oid:
    2327955
    origin:
    Herøya
    did:
    2449875
    destination:
    Vierow
  75. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  76. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  77. oid:
    2449875
    origin:
    Vierow
    did:
    2328146
    destination:
    Gunhildvågen
  78. oid:
    2449875
    origin:
    Vierow
    did:
    2327923
    destination:
    Oslo
  79. oid:
    2449875
    origin:
    Vierow
    did:
    2328234
    destination:
    Valsneset

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.

AI agent? Read the complete navigation and programming guide.