Kåfjorden ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T16:33:08Z.

Havn

havn_id:
2454663
navn:
Kåfjorden ankring
kode:
NOZKF
type:
Ankerplass
kommune:
Nordkapp
fylke:
Finnmark
lat:
70.900133
lon:
25.73616

Port-call and departure connections

34 results

  1. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328369
    destination:
    Bergeneset
  2. oid:
    2328369
    origin:
    Bergeneset
    did:
    2454663
    destination:
    Kåfjorden ankring
  3. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  4. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2454663
    destination:
    Kåfjorden ankring
  5. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  6. oid:
    2328369
    origin:
    Bergeneset
    did:
    2454663
    destination:
    Kåfjorden ankring
  7. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2454663
    destination:
    Kåfjorden ankring
  8. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328291
    destination:
    Stokmarknes
  9. oid:
    2328369
    origin:
    Bergeneset
    did:
    2454663
    destination:
    Kåfjorden ankring
  10. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  11. oid:
    2328369
    origin:
    Bergeneset
    did:
    2454663
    destination:
    Kåfjorden ankring
  12. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  13. oid:
    2328361
    origin:
    Tromsø
    did:
    2454663
    destination:
    Kåfjorden ankring
  14. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  15. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2454663
    destination:
    Kåfjorden ankring
  16. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  17. oid:
    2328369
    origin:
    Bergeneset
    did:
    2454663
    destination:
    Kåfjorden ankring
  18. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  19. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  20. oid:
    2328321
    origin:
    Alta
    did:
    2454663
    destination:
    Kåfjorden ankring
  21. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328336
    destination:
    Hasvik
  22. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2458670
    destination:
    Honningsvåg ankring
  23. oid:
    2328361
    origin:
    Tromsø
    did:
    2454663
    destination:
    Kåfjorden ankring
  24. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  25. oid:
    2451879
    origin:
    Lauksundet
    did:
    2454663
    destination:
    Kåfjorden ankring
  26. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  27. oid:
    2328321
    origin:
    Alta
    did:
    2454663
    destination:
    Kåfjorden ankring
  28. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  29. oid:
    2451879
    origin:
    Lauksundet
    did:
    2454663
    destination:
    Kåfjorden ankring
  30. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  31. oid:
    2328361
    origin:
    Tromsø
    did:
    2454663
    destination:
    Kåfjorden ankring
  32. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2450257
    destination:
    Rypefjord
  33. oid:
    2450257
    origin:
    Rypefjord
    did:
    2454663
    destination:
    Kåfjorden ankring
  34. oid:
    2454663
    origin:
    Kåfjorden ankring
    did:
    2328336
    destination:
    Hasvik

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.