Tanafjorden

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:11:33Z.

Havn

havn_id:
2353328
navn:
Tanafjorden
kode:
NOZTJ
type:
Sted i sjøen
kommune:
Gamvik
fylke:
Finnmark
lat:
70.63212
lon:
28.38522

Port-call and departure connections

56 results

  1. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328279
    destination:
    Narvik
  2. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328350
    destination:
    Mehamn
  3. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328327
    destination:
    Båtsfjord
  4. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  5. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  6. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  7. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  8. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  9. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  10. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2450247
    destination:
    Kuvika
  11. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328361
    destination:
    Tromsø
  12. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328361
    destination:
    Tromsø
  13. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328321
    destination:
    Alta
  14. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328321
    destination:
    Alta
  15. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328348
    destination:
    Leirpollen
  16. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328348
    destination:
    Leirpollen
  17. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328348
    destination:
    Leirpollen
  18. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328348
    destination:
    Leirpollen
  19. oid:
    2328375
    origin:
    Kvalsund
    did:
    2353328
    destination:
    Tanafjorden
  20. oid:
    2451489
    origin:
    Bergsfjord
    did:
    2353328
    destination:
    Tanafjorden
  21. oid:
    2328335
    origin:
    Hammerfest
    did:
    2353328
    destination:
    Tanafjorden
  22. oid:
    2328302
    origin:
    Hekkelstrand
    did:
    2353328
    destination:
    Tanafjorden
  23. oid:
    2328369
    origin:
    Bergeneset
    did:
    2353328
    destination:
    Tanafjorden
  24. oid:
    2447641
    origin:
    Barentshavet
    did:
    2353328
    destination:
    Tanafjorden
  25. oid:
    2447641
    origin:
    Barentshavet
    did:
    2353328
    destination:
    Tanafjorden
  26. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2353328
    destination:
    Tanafjorden
  27. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2353328
    destination:
    Tanafjorden
  28. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2353328
    destination:
    Tanafjorden
  29. oid:
    2328264
    origin:
    Harstad
    did:
    2353328
    destination:
    Tanafjorden
  30. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2353328
    destination:
    Tanafjorden
  31. oid:
    2451608
    origin:
    Akkarfjord
    did:
    2353328
    destination:
    Tanafjorden
  32. oid:
    2328356
    origin:
    Skjervøy
    did:
    2353328
    destination:
    Tanafjorden
  33. oid:
    2457510
    origin:
    Repparfjord
    did:
    2353328
    destination:
    Tanafjorden
  34. oid:
    2457510
    origin:
    Repparfjord
    did:
    2353328
    destination:
    Tanafjorden
  35. oid:
    2457510
    origin:
    Repparfjord
    did:
    2353328
    destination:
    Tanafjorden
  36. oid:
    2328321
    origin:
    Alta
    did:
    2353328
    destination:
    Tanafjorden
  37. oid:
    2328262
    origin:
    Glomfjord
    did:
    2353328
    destination:
    Tanafjorden
  38. oid:
    2450247
    origin:
    Kuvika
    did:
    2353328
    destination:
    Tanafjorden
  39. oid:
    2450247
    origin:
    Kuvika
    did:
    2353328
    destination:
    Tanafjorden
  40. oid:
    2450247
    origin:
    Kuvika
    did:
    2353328
    destination:
    Tanafjorden
  41. oid:
    2328337
    origin:
    Havøysund
    did:
    2353328
    destination:
    Tanafjorden
  42. oid:
    2328337
    origin:
    Havøysund
    did:
    2353328
    destination:
    Tanafjorden
  43. oid:
    2328337
    origin:
    Havøysund
    did:
    2353328
    destination:
    Tanafjorden
  44. oid:
    2328337
    origin:
    Havøysund
    did:
    2353328
    destination:
    Tanafjorden
  45. oid:
    2328327
    origin:
    Båtsfjord
    did:
    2353328
    destination:
    Tanafjorden
  46. oid:
    2328327
    origin:
    Båtsfjord
    did:
    2353328
    destination:
    Tanafjorden
  47. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328337
    destination:
    Havøysund
  48. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328337
    destination:
    Havøysund
  49. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328339
    destination:
    Honningsvåg
  50. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2447641
    destination:
    Barentshavet
  51. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2447641
    destination:
    Barentshavet
  52. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328331
    destination:
    Gjesvær
  53. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328343
    destination:
    Kirkenes
  54. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328335
    destination:
    Hammerfest
  55. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328322
    destination:
    Berlevåg
  56. oid:
    2353328
    origin:
    Tanafjorden
    did:
    2328363
    destination:
    Vadsø

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.