Langstein

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:45:41Z.

Havn

havn_id:
2328191
navn:
Langstein
kode:
NOLGS
type:
Havn
kommune:
Stjørdal
fylke:
Trøndelag
lat:
63.54547
lon:
10.88874

Port-call and departure connections

33 results

  1. oid:
    2328191
    origin:
    Langstein
    did:
    2450417
    destination:
    Sistranda
  2. oid:
    2328191
    origin:
    Langstein
    did:
    2328237
    destination:
    Vikan - Smøla
  3. oid:
    2328189
    origin:
    Kristiansund
    did:
    2328191
    destination:
    Langstein
  4. oid:
    2328251
    origin:
    Bodø
    did:
    2328191
    destination:
    Langstein
  5. oid:
    2328162
    origin:
    Freifjorden ankring
    did:
    2328191
    destination:
    Langstein
  6. oid:
    2457312
    origin:
    Bessaker
    did:
    2328191
    destination:
    Langstein
  7. oid:
    2457312
    origin:
    Bessaker
    did:
    2328191
    destination:
    Langstein
  8. oid:
    2457312
    origin:
    Bessaker
    did:
    2328191
    destination:
    Langstein
  9. oid:
    2328223
    origin:
    Trondheim
    did:
    2328191
    destination:
    Langstein
  10. oid:
    2328223
    origin:
    Trondheim
    did:
    2328191
    destination:
    Langstein
  11. oid:
    2452148
    origin:
    Nordskaget - Frøya
    did:
    2328191
    destination:
    Langstein
  12. oid:
    2452148
    origin:
    Nordskaget - Frøya
    did:
    2328191
    destination:
    Langstein
  13. oid:
    2454501
    origin:
    Hammarvika - Frøya
    did:
    2328191
    destination:
    Langstein
  14. oid:
    2454501
    origin:
    Hammarvika - Frøya
    did:
    2328191
    destination:
    Langstein
  15. oid:
    2328191
    origin:
    Langstein
    did:
    2328191
    destination:
    Langstein
  16. oid:
    2328191
    origin:
    Langstein
    did:
    2328191
    destination:
    Langstein
  17. oid:
    2328191
    origin:
    Langstein
    did:
    2328191
    destination:
    Langstein
  18. oid:
    2450417
    origin:
    Sistranda
    did:
    2328191
    destination:
    Langstein
  19. oid:
    2450417
    origin:
    Sistranda
    did:
    2328191
    destination:
    Langstein
  20. oid:
    2328191
    origin:
    Langstein
    did:
    2447466
    destination:
    Høgset
  21. oid:
    2328191
    origin:
    Langstein
    did:
    2447466
    destination:
    Høgset
  22. oid:
    2328191
    origin:
    Langstein
    did:
    2447394
    destination:
    Vingsand
  23. oid:
    2328191
    origin:
    Langstein
    did:
    2452148
    destination:
    Nordskaget - Frøya
  24. oid:
    2328191
    origin:
    Langstein
    did:
    2452148
    destination:
    Nordskaget - Frøya
  25. oid:
    2328191
    origin:
    Langstein
    did:
    2454501
    destination:
    Hammarvika - Frøya
  26. oid:
    2328191
    origin:
    Langstein
    did:
    2454501
    destination:
    Hammarvika - Frøya
  27. oid:
    2328191
    origin:
    Langstein
    did:
    2454501
    destination:
    Hammarvika - Frøya
  28. oid:
    2328191
    origin:
    Langstein
    did:
    2454501
    destination:
    Hammarvika - Frøya
  29. oid:
    2328191
    origin:
    Langstein
    did:
    2454501
    destination:
    Hammarvika - Frøya
  30. oid:
    2328191
    origin:
    Langstein
    did:
    2328232
    destination:
    Ålesund
  31. oid:
    2328191
    origin:
    Langstein
    did:
    2328162
    destination:
    Freifjorden ankring
  32. oid:
    2328191
    origin:
    Langstein
    did:
    2328162
    destination:
    Freifjorden ankring
  33. oid:
    2328191
    origin:
    Langstein
    did:
    2328743
    destination:
    Emden

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.