Lanesgrunnen - Tromsø

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T09:51:42Z.

Havn

havn_id:
2450408
navn:
Lanesgrunnen - Tromsø
kode:
not reported by source
type:
Sted i sjøen
kommune:
Tromsø
fylke:
Troms
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

30 results

  1. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328232
    destination:
    Ålesund
  2. oid:
    2463851
    origin:
    Ågskardet ferjekai
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  3. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2450409
    destination:
    Nordspissen - Tromsø
  4. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  5. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328361
    destination:
    Tromsø
  6. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2447641
    destination:
    Barentshavet
  7. oid:
    2328327
    origin:
    Båtsfjord
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  8. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2447641
    destination:
    Barentshavet
  9. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2447641
    destination:
    Barentshavet
  10. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2332022
    destination:
    Longyearbyen
  11. oid:
    2328361
    origin:
    Tromsø
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  12. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328225
    destination:
    Uthaug
  13. oid:
    2328225
    origin:
    Uthaug
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  14. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328225
    destination:
    Uthaug
  15. oid:
    2328232
    origin:
    Ålesund
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  16. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2454501
    destination:
    Hammarvika - Frøya
  17. oid:
    2328333
    origin:
    Hamnbukt - Porsanger
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  18. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328333
    destination:
    Hamnbukt - Porsanger
  19. oid:
    2328251
    origin:
    Bodø
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  20. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2451874
    destination:
    Maursundet
  21. oid:
    2465683
    origin:
    Snarbybukta ankring
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  22. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2328361
    destination:
    Tromsø
  23. oid:
    2328357
    origin:
    Sommarøy
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  24. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2452209
    destination:
    Nordlenangen
  25. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  26. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2456998
    destination:
    Ramfjordnes
  27. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  28. oid:
    2452209
    origin:
    Nordlenangen
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø
  29. oid:
    2450408
    origin:
    Lanesgrunnen - Tromsø
    did:
    2451874
    destination:
    Maursundet
  30. oid:
    2447367
    origin:
    Anfinnsletta
    did:
    2450408
    destination:
    Lanesgrunnen - Tromsø

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.