Allemannsdata
Manual search

Harstad ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

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

Havn

havn_id:
2452195
navn:
Harstad ankring
kode:
not reported by source
type:
Ankerplass
kommune:
Harstad
fylke:
Troms
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

25 results

  1. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2447367
    destination:
    Anfinnsletta
  2. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2465769
    destination:
    Jøvika - Senja
  3. oid:
    2341653
    origin:
    Torsken
    did:
    2452195
    destination:
    Harstad ankring
  4. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328264
    destination:
    Harstad
  5. oid:
    2328361
    origin:
    Tromsø
    did:
    2452195
    destination:
    Harstad ankring
  6. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328264
    destination:
    Harstad
  7. oid:
    2328264
    origin:
    Harstad
    did:
    2452195
    destination:
    Harstad ankring
  8. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328321
    destination:
    Alta
  9. oid:
    2454528
    origin:
    Skålevik
    did:
    2452195
    destination:
    Harstad ankring
  10. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328291
    destination:
    Stokmarknes
  11. oid:
    2451561
    origin:
    Bogøy
    did:
    2452195
    destination:
    Harstad ankring
  12. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328291
    destination:
    Stokmarknes
  13. oid:
    2451561
    origin:
    Bogøy
    did:
    2452195
    destination:
    Harstad ankring
  14. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328291
    destination:
    Stokmarknes
  15. oid:
    2328252
    origin:
    Bogen
    did:
    2452195
    destination:
    Harstad ankring
  16. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328291
    destination:
    Stokmarknes
  17. oid:
    2451561
    origin:
    Bogøy
    did:
    2452195
    destination:
    Harstad ankring
  18. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328335
    destination:
    Hammerfest
  19. oid:
    2451487
    origin:
    Svolvær Osan
    did:
    2452195
    destination:
    Harstad ankring
  20. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2328264
    destination:
    Harstad
  21. oid:
    2458542
    origin:
    Lødingen ankring
    did:
    2452195
    destination:
    Harstad ankring
  22. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2450225
    destination:
    Botnhamn
  23. oid:
    2452195
    origin:
    Harstad ankring
    did:
    2451561
    destination:
    Bogøy
  24. oid:
    2451561
    origin:
    Bogøy
    did:
    2452195
    destination:
    Harstad ankring
  25. oid:
    2328281
    origin:
    Ramsund
    did:
    2452195
    destination:
    Harstad 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.