Ylvingen

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T09:01:15Z.

Havn

havn_id:
2450412
navn:
Ylvingen
kode:
NOZVD
type:
Sted i sjøen
kommune:
Vega
fylke:
Nordland
lat:
65.64465
lon:
12.17388

Port-call and departure connections

54 results

  1. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450219
    destination:
    Vormedal
  2. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450219
    destination:
    Vormedal
  3. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328286
    destination:
    Sandnessjøen
  4. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328286
    destination:
    Sandnessjøen
  5. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328361
    destination:
    Tromsø
  6. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328290
    destination:
    Sortland
  7. oid:
    2450412
    origin:
    Ylvingen
    did:
    2464676
    destination:
    Bindal
  8. oid:
    2450412
    origin:
    Ylvingen
    did:
    2464676
    destination:
    Bindal
  9. oid:
    2450412
    origin:
    Ylvingen
    did:
    2464676
    destination:
    Bindal
  10. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328209
    destination:
    Rørvik
  11. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328209
    destination:
    Rørvik
  12. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328209
    destination:
    Rørvik
  13. oid:
    2353256
    origin:
    Lovund
    did:
    2450412
    destination:
    Ylvingen
  14. oid:
    2328189
    origin:
    Kristiansund
    did:
    2450412
    destination:
    Ylvingen
  15. oid:
    2450240
    origin:
    Herøy
    did:
    2450412
    destination:
    Ylvingen
  16. oid:
    2450240
    origin:
    Herøy
    did:
    2450412
    destination:
    Ylvingen
  17. oid:
    2450240
    origin:
    Herøy
    did:
    2450412
    destination:
    Ylvingen
  18. oid:
    2450240
    origin:
    Herøy
    did:
    2450412
    destination:
    Ylvingen
  19. oid:
    2328255
    origin:
    Brønnøysund
    did:
    2450412
    destination:
    Ylvingen
  20. oid:
    2328255
    origin:
    Brønnøysund
    did:
    2450412
    destination:
    Ylvingen
  21. oid:
    2328251
    origin:
    Bodø
    did:
    2450412
    destination:
    Ylvingen
  22. oid:
    2328251
    origin:
    Bodø
    did:
    2450412
    destination:
    Ylvingen
  23. oid:
    2328251
    origin:
    Bodø
    did:
    2450412
    destination:
    Ylvingen
  24. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2450412
    destination:
    Ylvingen
  25. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2450412
    destination:
    Ylvingen
  26. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2450412
    destination:
    Ylvingen
  27. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2450412
    destination:
    Ylvingen
  28. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2450412
    destination:
    Ylvingen
  29. oid:
    2328209
    origin:
    Rørvik
    did:
    2450412
    destination:
    Ylvingen
  30. oid:
    2328209
    origin:
    Rørvik
    did:
    2450412
    destination:
    Ylvingen
  31. oid:
    2328209
    origin:
    Rørvik
    did:
    2450412
    destination:
    Ylvingen
  32. oid:
    2328264
    origin:
    Harstad
    did:
    2450412
    destination:
    Ylvingen
  33. oid:
    2457041
    origin:
    Nordfold
    did:
    2450412
    destination:
    Ylvingen
  34. oid:
    2464676
    origin:
    Bindal
    did:
    2450412
    destination:
    Ylvingen
  35. oid:
    2464676
    origin:
    Bindal
    did:
    2450412
    destination:
    Ylvingen
  36. oid:
    2464676
    origin:
    Bindal
    did:
    2450412
    destination:
    Ylvingen
  37. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2450412
    destination:
    Ylvingen
  38. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2450412
    destination:
    Ylvingen
  39. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2450412
    destination:
    Ylvingen
  40. oid:
    2450219
    origin:
    Vormedal
    did:
    2450412
    destination:
    Ylvingen
  41. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450250
    destination:
    Myre-Øksnes
  42. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450250
    destination:
    Myre-Øksnes
  43. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450250
    destination:
    Myre-Øksnes
  44. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450250
    destination:
    Myre-Øksnes
  45. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450250
    destination:
    Myre-Øksnes
  46. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328251
    destination:
    Bodø
  47. oid:
    2450412
    origin:
    Ylvingen
    did:
    2328255
    destination:
    Brønnøysund
  48. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450240
    destination:
    Herøy
  49. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450240
    destination:
    Herøy
  50. oid:
    2450412
    origin:
    Ylvingen
    did:
    2450240
    destination:
    Herøy
  51. oid:
    2450412
    origin:
    Ylvingen
    did:
    2457040
    destination:
    Sørarnøy
  52. oid:
    2450412
    origin:
    Ylvingen
    did:
    2457040
    destination:
    Sørarnøy
  53. oid:
    2450412
    origin:
    Ylvingen
    did:
    2457040
    destination:
    Sørarnøy
  54. oid:
    2450412
    origin:
    Ylvingen
    did:
    2457040
    destination:
    Sørarnø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.