Allemannsdata
Manual search

Ona

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T08:06:05Z.

Havn

havn_id:
2451465
navn:
Ona
kode:
not reported by source
type:
Sted i sjøen
kommune:
Ålesund
fylke:
Møre og Romsdal
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

38 results

  1. oid:
    2451465
    origin:
    Ona
    did:
    2328232
    destination:
    Ålesund
  2. oid:
    2328361
    origin:
    Tromsø
    did:
    2451465
    destination:
    Ona
  3. oid:
    2451465
    origin:
    Ona
    did:
    2447769
    destination:
    Mjølstadneset
  4. oid:
    2328236
    origin:
    Eggesbønes
    did:
    2451465
    destination:
    Ona
  5. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  6. oid:
    2328232
    origin:
    Ålesund
    did:
    2451465
    destination:
    Ona
  7. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  8. oid:
    2447769
    origin:
    Mjølstadneset
    did:
    2451465
    destination:
    Ona
  9. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  10. oid:
    2328236
    origin:
    Eggesbønes
    did:
    2451465
    destination:
    Ona
  11. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  12. oid:
    2328236
    origin:
    Eggesbønes
    did:
    2451465
    destination:
    Ona
  13. oid:
    2451465
    origin:
    Ona
    did:
    2447769
    destination:
    Mjølstadneset
  14. oid:
    2447769
    origin:
    Mjølstadneset
    did:
    2451465
    destination:
    Ona
  15. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  16. oid:
    2447769
    origin:
    Mjølstadneset
    did:
    2451465
    destination:
    Ona
  17. oid:
    2451465
    origin:
    Ona
    did:
    2328236
    destination:
    Eggesbønes
  18. oid:
    2328236
    origin:
    Eggesbønes
    did:
    2451465
    destination:
    Ona
  19. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  20. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2451465
    destination:
    Ona
  21. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  22. oid:
    2328232
    origin:
    Ålesund
    did:
    2451465
    destination:
    Ona
  23. oid:
    2451465
    origin:
    Ona
    did:
    2328232
    destination:
    Ålesund
  24. oid:
    2447414
    origin:
    Austevoll
    did:
    2451465
    destination:
    Ona
  25. oid:
    2329137
    origin:
    Tyborøn
    did:
    2451465
    destination:
    Ona
  26. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  27. oid:
    2328189
    origin:
    Kristiansund
    did:
    2451465
    destination:
    Ona
  28. oid:
    2451465
    origin:
    Ona
    did:
    2328189
    destination:
    Kristiansund
  29. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  30. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2451465
    destination:
    Ona
  31. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  32. oid:
    2328168
    origin:
    Ellingsøy
    did:
    2451465
    destination:
    Ona
  33. oid:
    2451465
    origin:
    Ona
    did:
    2328168
    destination:
    Ellingsøy
  34. oid:
    2328232
    origin:
    Ålesund
    did:
    2451465
    destination:
    Ona
  35. oid:
    2451465
    origin:
    Ona
    did:
    2450240
    destination:
    Herøy
  36. oid:
    2328234
    origin:
    Valsneset
    did:
    2451465
    destination:
    Ona
  37. oid:
    2451465
    origin:
    Ona
    did:
    2328200
    destination:
    Molde
  38. oid:
    2336671
    origin:
    Cullivoe, Yell
    did:
    2451465
    destination:
    Ona

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.