Napp

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:56:48Z.

Havn

havn_id:
2457889
navn:
Napp
kode:
NO888
type:
Havn
kommune:
Flakstad
fylke:
Nordland
lat:
68.129805
lon:
13.440035

Port-call and departure connections

58 results

  1. oid:
    2457889
    origin:
    Napp
    did:
    2328296
    destination:
    Tovik
  2. oid:
    2457889
    origin:
    Napp
    did:
    2353246
    destination:
    Inndyr
  3. oid:
    2457889
    origin:
    Napp
    did:
    2353331
    destination:
    Trollfjorden
  4. oid:
    2457889
    origin:
    Napp
    did:
    2328266
    destination:
    Henningsvær
  5. oid:
    2457889
    origin:
    Napp
    did:
    2328291
    destination:
    Stokmarknes
  6. oid:
    2457889
    origin:
    Napp
    did:
    2353228
    destination:
    Blokken
  7. oid:
    2457889
    origin:
    Napp
    did:
    2464662
    destination:
    Gavlfjorden
  8. oid:
    2457889
    origin:
    Napp
    did:
    2464662
    destination:
    Gavlfjorden
  9. oid:
    2457889
    origin:
    Napp
    did:
    2464662
    destination:
    Gavlfjorden
  10. oid:
    2457889
    origin:
    Napp
    did:
    2328293
    destination:
    Stø
  11. oid:
    2457889
    origin:
    Napp
    did:
    2328272
    destination:
    Lødingen
  12. oid:
    2457889
    origin:
    Napp
    did:
    2447367
    destination:
    Anfinnsletta
  13. oid:
    2457889
    origin:
    Napp
    did:
    2447367
    destination:
    Anfinnsletta
  14. oid:
    2457889
    origin:
    Napp
    did:
    2328260
    destination:
    Fjelldal
  15. oid:
    2457889
    origin:
    Napp
    did:
    2451866
    destination:
    Fiskebøl
  16. oid:
    2457889
    origin:
    Napp
    did:
    2458542
    destination:
    Lødingen ankring
  17. oid:
    2457889
    origin:
    Napp
    did:
    2341607
    destination:
    Stamsund
  18. oid:
    2457889
    origin:
    Napp
    did:
    2452157
    destination:
    Bognes
  19. oid:
    2328285
    origin:
    Salangsverket
    did:
    2457889
    destination:
    Napp
  20. oid:
    2328276
    origin:
    Moskenes
    did:
    2457889
    destination:
    Napp
  21. oid:
    2328276
    origin:
    Moskenes
    did:
    2457889
    destination:
    Napp
  22. oid:
    2353227
    origin:
    Barstrand
    did:
    2457889
    destination:
    Napp
  23. oid:
    2353227
    origin:
    Barstrand
    did:
    2457889
    destination:
    Napp
  24. oid:
    2328251
    origin:
    Bodø
    did:
    2457889
    destination:
    Napp
  25. oid:
    2457511
    origin:
    Ramberg
    did:
    2457889
    destination:
    Napp
  26. oid:
    2328250
    origin:
    Ballstad
    did:
    2457889
    destination:
    Napp
  27. oid:
    2451490
    origin:
    Nusfjord
    did:
    2457889
    destination:
    Napp
  28. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2457889
    destination:
    Napp
  29. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2457889
    destination:
    Napp
  30. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2457889
    destination:
    Napp
  31. oid:
    2450250
    origin:
    Myre-Øksnes
    did:
    2457889
    destination:
    Napp
  32. oid:
    2334641
    origin:
    Hvide Sande
    did:
    2457889
    destination:
    Napp
  33. oid:
    2328264
    origin:
    Harstad
    did:
    2457889
    destination:
    Napp
  34. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2457889
    destination:
    Napp
  35. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2457889
    destination:
    Napp
  36. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2457889
    destination:
    Napp
  37. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2457889
    destination:
    Napp
  38. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2457889
    destination:
    Napp
  39. oid:
    2451868
    origin:
    Reine Sjøen
    did:
    2457889
    destination:
    Napp
  40. oid:
    2451868
    origin:
    Reine Sjøen
    did:
    2457889
    destination:
    Napp
  41. oid:
    2451868
    origin:
    Reine Sjøen
    did:
    2457889
    destination:
    Napp
  42. oid:
    2447759
    origin:
    Fornes
    did:
    2457889
    destination:
    Napp
  43. oid:
    2456882
    origin:
    Årstein-Gratangen
    did:
    2457889
    destination:
    Napp
  44. oid:
    2456882
    origin:
    Årstein-Gratangen
    did:
    2457889
    destination:
    Napp
  45. oid:
    2467367
    origin:
    Sortlandsundet nord ankring
    did:
    2457889
    destination:
    Napp
  46. oid:
    2353228
    origin:
    Blokken
    did:
    2457889
    destination:
    Napp
  47. oid:
    2328282
    origin:
    Reine
    did:
    2457889
    destination:
    Napp
  48. oid:
    2457889
    origin:
    Napp
    did:
    2447641
    destination:
    Barentshavet
  49. oid:
    2457889
    origin:
    Napp
    did:
    2447641
    destination:
    Barentshavet
  50. oid:
    2457889
    origin:
    Napp
    did:
    2467361
    destination:
    Bogen ankring - Evenes
  51. oid:
    2457889
    origin:
    Napp
    did:
    2334641
    destination:
    Hvide Sande
  52. oid:
    2457889
    origin:
    Napp
    did:
    2450250
    destination:
    Myre-Øksnes
  53. oid:
    2457889
    origin:
    Napp
    did:
    2450250
    destination:
    Myre-Øksnes
  54. oid:
    2457889
    origin:
    Napp
    did:
    2450250
    destination:
    Myre-Øksnes
  55. oid:
    2457889
    origin:
    Napp
    did:
    2328251
    destination:
    Bodø
  56. oid:
    2457889
    origin:
    Napp
    did:
    2353227
    destination:
    Barstrand
  57. oid:
    2457889
    origin:
    Napp
    did:
    2328276
    destination:
    Moskenes
  58. oid:
    2457889
    origin:
    Napp
    did:
    2328292
    destination:
    Straumsjøen

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.