Finnfjorden ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T09:33:37Z.

Havn

havn_id:
2467364
navn:
Finnfjorden ankring
kode:
NOZIA
type:
Ankerplass
kommune:
Senja
fylke:
Troms
lat:
69.221117
lon:
18.01795

Port-call and departure connections

32 results

  1. oid:
    2328305
    origin:
    Leknes
    did:
    2467364
    destination:
    Finnfjorden ankring
  2. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2467369
    destination:
    Sørreisa ankring
  3. oid:
    2464251
    origin:
    Kårvika ankring
    did:
    2467364
    destination:
    Finnfjorden ankring
  4. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  5. oid:
    2353331
    origin:
    Trollfjorden
    did:
    2467364
    destination:
    Finnfjorden ankring
  6. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2464251
    destination:
    Kårvika ankring
  7. oid:
    2328351
    origin:
    Reinfjord
    did:
    2467364
    destination:
    Finnfjorden ankring
  8. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328341
    destination:
    Jøvik
  9. oid:
    2458542
    origin:
    Lødingen ankring
    did:
    2467364
    destination:
    Finnfjorden ankring
  10. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328204
    destination:
    Namsos
  11. oid:
    2328328
    origin:
    Finnsnes
    did:
    2467364
    destination:
    Finnfjorden ankring
  12. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328301
    destination:
    Finnfjordbotn
  13. oid:
    2328348
    origin:
    Leirpollen
    did:
    2467364
    destination:
    Finnfjorden ankring
  14. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328301
    destination:
    Finnfjordbotn
  15. oid:
    2329277
    origin:
    Belfast
    did:
    2467364
    destination:
    Finnfjorden ankring
  16. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328361
    destination:
    Tromsø
  17. oid:
    2328301
    origin:
    Finnfjordbotn
    did:
    2467364
    destination:
    Finnfjorden ankring
  18. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328301
    destination:
    Finnfjordbotn
  19. oid:
    2329277
    origin:
    Belfast
    did:
    2467364
    destination:
    Finnfjorden ankring
  20. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2447759
    destination:
    Fornes
  21. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2467364
    destination:
    Finnfjorden ankring
  22. oid:
    2450225
    origin:
    Botnhamn
    did:
    2467364
    destination:
    Finnfjorden ankring
  23. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328369
    destination:
    Bergeneset
  24. oid:
    2328264
    origin:
    Harstad
    did:
    2467364
    destination:
    Finnfjorden ankring
  25. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2451879
    destination:
    Lauksundet
  26. oid:
    2328356
    origin:
    Skjervøy
    did:
    2467364
    destination:
    Finnfjorden ankring
  27. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328287
    destination:
    Sjøvegan
  28. oid:
    2328361
    origin:
    Tromsø
    did:
    2467364
    destination:
    Finnfjorden ankring
  29. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2447479
    destination:
    Malangen
  30. oid:
    2467363
    origin:
    Årbogen ankring
    did:
    2467364
    destination:
    Finnfjorden ankring
  31. oid:
    2467364
    origin:
    Finnfjorden ankring
    did:
    2328340
    destination:
    Husøy - Lenvik
  32. oid:
    2328340
    origin:
    Husøy - Lenvik
    did:
    2467364
    destination:
    Finnfjorden 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.