Allemannsdata
Manual search

Tyrhaug ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

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

Havn

havn_id:
2467357
navn:
Tyrhaug ankring
kode:
not reported by source
type:
Ankerplass
kommune:
Smøla
fylke:
Møre og Romsdal
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

49 results

  1. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328237
    destination:
    Vikan - Smøla
  2. oid:
    2328234
    origin:
    Valsneset
    did:
    2467357
    destination:
    Tyrhaug ankring
  3. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2341593
    destination:
    Smøla
  4. oid:
    2447413
    origin:
    Flesa
    did:
    2467357
    destination:
    Tyrhaug ankring
  5. oid:
    2450219
    origin:
    Vormedal
    did:
    2467357
    destination:
    Tyrhaug ankring
  6. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328189
    destination:
    Kristiansund
  7. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328239
    destination:
    Tjeldbergodden
  8. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328197
    destination:
    Lysøysund
  9. oid:
    2328180
    origin:
    Hestvika
    did:
    2467357
    destination:
    Tyrhaug ankring
  10. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328189
    destination:
    Kristiansund
  11. oid:
    2461664
    origin:
    Hemnskjela ankring
    did:
    2467357
    destination:
    Tyrhaug ankring
  12. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2461664
    destination:
    Hemnskjela ankring
  13. oid:
    2461664
    origin:
    Hemnskjela ankring
    did:
    2467357
    destination:
    Tyrhaug ankring
  14. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2461664
    destination:
    Hemnskjela ankring
  15. oid:
    2461664
    origin:
    Hemnskjela ankring
    did:
    2467357
    destination:
    Tyrhaug ankring
  16. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2461664
    destination:
    Hemnskjela ankring
  17. oid:
    2461664
    origin:
    Hemnskjela ankring
    did:
    2467357
    destination:
    Tyrhaug ankring
  18. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2451567
    destination:
    Stokksund
  19. oid:
    2328223
    origin:
    Trondheim
    did:
    2467357
    destination:
    Tyrhaug ankring
  20. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2461820
    destination:
    Lekaflaket Ankring
  21. oid:
    2457312
    origin:
    Bessaker
    did:
    2467357
    destination:
    Tyrhaug ankring
  22. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2460955
    destination:
    Kvernhusvika
  23. oid:
    2450417
    origin:
    Sistranda
    did:
    2467357
    destination:
    Tyrhaug ankring
  24. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328189
    destination:
    Kristiansund
  25. oid:
    2450417
    origin:
    Sistranda
    did:
    2467357
    destination:
    Tyrhaug ankring
  26. oid:
    2452148
    origin:
    Nordskaget - Frøya
    did:
    2467357
    destination:
    Tyrhaug ankring
  27. oid:
    2452148
    origin:
    Nordskaget - Frøya
    did:
    2467357
    destination:
    Tyrhaug ankring
  28. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2460955
    destination:
    Kvernhusvika
  29. oid:
    2450417
    origin:
    Sistranda
    did:
    2467357
    destination:
    Tyrhaug ankring
  30. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2452148
    destination:
    Nordskaget - Frøya
  31. oid:
    2452148
    origin:
    Nordskaget - Frøya
    did:
    2467357
    destination:
    Tyrhaug ankring
  32. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328189
    destination:
    Kristiansund
  33. oid:
    2457312
    origin:
    Bessaker
    did:
    2467357
    destination:
    Tyrhaug ankring
  34. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2341687
    destination:
    Vevang
  35. oid:
    2447765
    origin:
    Ottersøy
    did:
    2467357
    destination:
    Tyrhaug ankring
  36. oid:
    2454501
    origin:
    Hammarvika - Frøya
    did:
    2467357
    destination:
    Tyrhaug ankring
  37. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2454501
    destination:
    Hammarvika - Frøya
  38. oid:
    2451567
    origin:
    Stokksund
    did:
    2467357
    destination:
    Tyrhaug ankring
  39. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328223
    destination:
    Trondheim
  40. oid:
    2328171
    origin:
    Follafoss
    did:
    2467357
    destination:
    Tyrhaug ankring
  41. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328171
    destination:
    Follafoss
  42. oid:
    2328171
    origin:
    Follafoss
    did:
    2467357
    destination:
    Tyrhaug ankring
  43. oid:
    2450417
    origin:
    Sistranda
    did:
    2467357
    destination:
    Tyrhaug ankring
  44. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2464385
    destination:
    Garten
  45. oid:
    2456502
    origin:
    Sandstad
    did:
    2467357
    destination:
    Tyrhaug ankring
  46. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2328233
    destination:
    Åndalsnes
  47. oid:
    2328223
    origin:
    Trondheim
    did:
    2467357
    destination:
    Tyrhaug ankring
  48. oid:
    2467357
    origin:
    Tyrhaug ankring
    did:
    2465551
    destination:
    Roan
  49. oid:
    2457196
    origin:
    Øye
    did:
    2467357
    destination:
    Tyrhaug 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.