Honningsvåg ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:50:26Z.

Havn

havn_id:
2458670
navn:
Honningsvåg ankring
kode:
NOZHY
type:
Ankerplass
kommune:
Nordkapp
fylke:
Finnmark
lat:
70.983372
lon:
25.948763

Port-call and departure connections

31 results

  1. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328361
    destination:
    Tromsø
  2. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328361
    destination:
    Tromsø
  3. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328112
    destination:
    Svelgen
  4. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2353305
    destination:
    Lafjorden
  5. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2353305
    destination:
    Lafjorden
  6. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328348
    destination:
    Leirpollen
  7. oid:
    2447354
    origin:
    Skarsvåg ankring
    did:
    2458670
    destination:
    Honningsvåg ankring
  8. oid:
    2328301
    origin:
    Finnfjordbotn
    did:
    2458670
    destination:
    Honningsvåg ankring
  9. oid:
    2330411
    origin:
    Murmansk
    did:
    2458670
    destination:
    Honningsvåg ankring
  10. oid:
    2447641
    origin:
    Barentshavet
    did:
    2458670
    destination:
    Honningsvåg ankring
  11. oid:
    2447641
    origin:
    Barentshavet
    did:
    2458670
    destination:
    Honningsvåg ankring
  12. oid:
    2447641
    origin:
    Barentshavet
    did:
    2458670
    destination:
    Honningsvåg ankring
  13. oid:
    2447641
    origin:
    Barentshavet
    did:
    2458670
    destination:
    Honningsvåg ankring
  14. oid:
    2328348
    origin:
    Leirpollen
    did:
    2458670
    destination:
    Honningsvåg ankring
  15. oid:
    2328348
    origin:
    Leirpollen
    did:
    2458670
    destination:
    Honningsvåg ankring
  16. oid:
    2328348
    origin:
    Leirpollen
    did:
    2458670
    destination:
    Honningsvåg ankring
  17. oid:
    2353305
    origin:
    Lafjorden
    did:
    2458670
    destination:
    Honningsvåg ankring
  18. oid:
    2353305
    origin:
    Lafjorden
    did:
    2458670
    destination:
    Honningsvåg ankring
  19. oid:
    2328361
    origin:
    Tromsø
    did:
    2458670
    destination:
    Honningsvåg ankring
  20. oid:
    2328337
    origin:
    Havøysund
    did:
    2458670
    destination:
    Honningsvåg ankring
  21. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2458670
    destination:
    Honningsvåg ankring
  22. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2458670
    destination:
    Honningsvåg ankring
  23. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2458670
    destination:
    Honningsvåg ankring
  24. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328339
    destination:
    Honningsvåg
  25. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328339
    destination:
    Honningsvåg
  26. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2447641
    destination:
    Barentshavet
  27. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2447641
    destination:
    Barentshavet
  28. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2447641
    destination:
    Barentshavet
  29. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2450257
    destination:
    Rypefjord
  30. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328301
    destination:
    Finnfjordbotn
  31. oid:
    2458670
    origin:
    Honningsvåg ankring
    did:
    2328182
    destination:
    Holla

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.