Narvik - Vidrek ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:07:37Z.

Havn

havn_id:
2466379
navn:
Narvik - Vidrek ankring
kode:
NOZVR
type:
Ankerplass
kommune:
Narvik
fylke:
Nordland
lat:
68.406888
lon:
17.165108

Port-call and departure connections

32 results

  1. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328279
    destination:
    Narvik
  2. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328291
    destination:
    Stokmarknes
  3. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328260
    destination:
    Fjelldal
  4. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328308
    destination:
    Halsa Meløy
  5. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328254
    destination:
    Brettesnes
  6. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328264
    destination:
    Harstad
  7. oid:
    2328189
    origin:
    Kristiansund
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  8. oid:
    2328258
    origin:
    Evenestangen
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  9. oid:
    2466378
    origin:
    Narvik - Herjangen ankring
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  10. oid:
    2467362
    origin:
    Tømmervika Ankring
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  11. oid:
    2451561
    origin:
    Bogøy
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  12. oid:
    2451561
    origin:
    Bogøy
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  13. oid:
    2451561
    origin:
    Bogøy
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  14. oid:
    2451561
    origin:
    Bogøy
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  15. oid:
    2450257
    origin:
    Rypefjord
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  16. oid:
    2451487
    origin:
    Svolvær Osan
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  17. oid:
    2328254
    origin:
    Brettesnes
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  18. oid:
    2328272
    origin:
    Lødingen
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  19. oid:
    2452159
    origin:
    Grytøya
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  20. oid:
    2329655
    origin:
    Teesport
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  21. oid:
    2328290
    origin:
    Sortland
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  22. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  23. oid:
    2328279
    origin:
    Narvik
    did:
    2466379
    destination:
    Narvik - Vidrek ankring
  24. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328302
    destination:
    Hekkelstrand
  25. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2328251
    destination:
    Bodø
  26. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  27. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  28. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  29. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  30. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  31. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2451561
    destination:
    Bogøy
  32. oid:
    2466379
    origin:
    Narvik - Vidrek ankring
    did:
    2353311
    destination:
    Narvikbukta ankring

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.