Allemannsdata
Manual search

Askvoll ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T05:31:07Z.

Havn

havn_id:
2467318
navn:
Askvoll ankring
kode:
not reported by source
type:
Ankerplass
kommune:
Askvoll
fylke:
Vestland
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

49 results

  1. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2451922
    destination:
    Gjøsundet
  2. oid:
    2328084
    origin:
    Florø
    did:
    2467318
    destination:
    Askvoll ankring
  3. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2329112
    destination:
    Skagen
  4. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2467318
    destination:
    Askvoll ankring
  5. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328274
    destination:
    Mo i Rana
  6. oid:
    2327904
    origin:
    Drammen
    did:
    2467318
    destination:
    Askvoll ankring
  7. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2467318
    destination:
    Askvoll ankring
  8. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2327994
    destination:
    Høllen
  9. oid:
    2329137
    origin:
    Tyborøn
    did:
    2467318
    destination:
    Askvoll ankring
  10. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2447414
    destination:
    Austevoll
  11. oid:
    2467182
    origin:
    Raunefjorden
    did:
    2467318
    destination:
    Askvoll ankring
  12. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2461754
    destination:
    Brekke
  13. oid:
    2328084
    origin:
    Florø
    did:
    2467318
    destination:
    Askvoll ankring
  14. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328084
    destination:
    Florø
  15. oid:
    2328084
    origin:
    Florø
    did:
    2467318
    destination:
    Askvoll ankring
  16. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328084
    destination:
    Florø
  17. oid:
    2461754
    origin:
    Brekke
    did:
    2467318
    destination:
    Askvoll ankring
  18. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2451828
    destination:
    Buefjorden
  19. oid:
    2447388
    origin:
    Haugsøytangen ankring
    did:
    2467318
    destination:
    Askvoll ankring
  20. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2447388
    destination:
    Haugsøytangen ankring
  21. oid:
    2465373
    origin:
    Davika ankring
    did:
    2467318
    destination:
    Askvoll ankring
  22. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328149
    destination:
    Iglandsvik
  23. oid:
    2450362
    origin:
    Strandvikflaket ankring
    did:
    2467318
    destination:
    Askvoll ankring
  24. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328236
    destination:
    Eggesbønes
  25. oid:
    2328236
    origin:
    Eggesbønes
    did:
    2467318
    destination:
    Askvoll ankring
  26. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328100
    destination:
    Måløy
  27. oid:
    2451771
    origin:
    Hyllestad
    did:
    2467318
    destination:
    Askvoll ankring
  28. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2341598
    destination:
    Solund
  29. oid:
    2328115
    origin:
    Vadheim
    did:
    2467318
    destination:
    Askvoll ankring
  30. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328084
    destination:
    Florø
  31. oid:
    2328112
    origin:
    Svelgen
    did:
    2467318
    destination:
    Askvoll ankring
  32. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2341598
    destination:
    Solund
  33. oid:
    2461754
    origin:
    Brekke
    did:
    2467318
    destination:
    Askvoll ankring
  34. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2467324
    destination:
    Hyen ytre ankring
  35. oid:
    2328112
    origin:
    Svelgen
    did:
    2467318
    destination:
    Askvoll ankring
  36. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328100
    destination:
    Måløy
  37. oid:
    2328112
    origin:
    Svelgen
    did:
    2467318
    destination:
    Askvoll ankring
  38. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328112
    destination:
    Svelgen
  39. oid:
    2328112
    origin:
    Svelgen
    did:
    2467318
    destination:
    Askvoll ankring
  40. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2467216
    destination:
    Ytre Steinsund
  41. oid:
    2461754
    origin:
    Brekke
    did:
    2467318
    destination:
    Askvoll ankring
  42. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2451562
    destination:
    Sognefjorden
  43. oid:
    2456441
    origin:
    Lutelandet
    did:
    2467318
    destination:
    Askvoll ankring
  44. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2451562
    destination:
    Sognefjorden
  45. oid:
    2451562
    origin:
    Sognefjorden
    did:
    2467318
    destination:
    Askvoll ankring
  46. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2447399
    destination:
    Fonnes
  47. oid:
    2447399
    origin:
    Fonnes
    did:
    2467318
    destination:
    Askvoll ankring
  48. oid:
    2467318
    origin:
    Askvoll ankring
    did:
    2328100
    destination:
    Måløy
  49. oid:
    2447478
    origin:
    Rutletangen
    did:
    2467318
    destination:
    Askvoll 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.

AI agent? Read the complete navigation and programming guide.