Nyelv

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T15:47:32Z.

Havn

havn_id:
2447764
navn:
Nyelv
kode:
NONYE
type:
Havn
kommune:
Unjárga Nesseby
fylke:
Finnmark
lat:
70.0758
lon:
28.86934

Port-call and departure connections

46 results

  1. oid:
    2328363
    origin:
    Vadsø
    did:
    2447764
    destination:
    Nyelv
  2. oid:
    2328343
    origin:
    Kirkenes
    did:
    2447764
    destination:
    Nyelv
  3. oid:
    2328343
    origin:
    Kirkenes
    did:
    2447764
    destination:
    Nyelv
  4. oid:
    2328343
    origin:
    Kirkenes
    did:
    2447764
    destination:
    Nyelv
  5. oid:
    2328369
    origin:
    Bergeneset
    did:
    2447764
    destination:
    Nyelv
  6. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  7. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  8. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  9. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  10. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  11. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  12. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  13. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  14. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  15. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  16. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  17. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  18. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  19. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  20. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  21. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  22. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  23. oid:
    2353247
    origin:
    Jakobsnes
    did:
    2447764
    destination:
    Nyelv
  24. oid:
    2447764
    origin:
    Nyelv
    did:
    2330484
    destination:
    Stettin
  25. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  26. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  27. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  28. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  29. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  30. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  31. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  32. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  33. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  34. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  35. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  36. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  37. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  38. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  39. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  40. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  41. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  42. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  43. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  44. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  45. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes
  46. oid:
    2447764
    origin:
    Nyelv
    did:
    2353247
    destination:
    Jakobsnes

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.