Stanlow

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T15:57:35Z.

Havn

havn_id:
2329636
navn:
Stanlow
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
52.5833333333333
lon:
-2.3

Port-call and departure connections

37 results

  1. oid:
    2329636
    origin:
    Stanlow
    did:
    2328034
    destination:
    Kårstø
  2. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  3. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  4. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  5. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  6. oid:
    2329636
    origin:
    Stanlow
    did:
    2328053
    destination:
    Falkeidflæet ankring
  7. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  8. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  9. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  10. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  11. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  12. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  13. oid:
    2327995
    origin:
    Kristiansand
    did:
    2329636
    destination:
    Stanlow
  14. oid:
    2328189
    origin:
    Kristiansund
    did:
    2329636
    destination:
    Stanlow
  15. oid:
    2329636
    origin:
    Stanlow
    did:
    2328123
    destination:
    Fonnesflaket ankring
  16. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  17. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  18. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  19. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  20. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  21. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  22. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  23. oid:
    2329636
    origin:
    Stanlow
    did:
    2328053
    destination:
    Falkeidflæet ankring
  24. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  25. oid:
    2329636
    origin:
    Stanlow
    did:
    2328034
    destination:
    Kårstø
  26. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  27. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  28. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  29. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  30. oid:
    2329636
    origin:
    Stanlow
    did:
    2328053
    destination:
    Falkeidflæet ankring
  31. oid:
    2328034
    origin:
    Kårstø
    did:
    2329636
    destination:
    Stanlow
  32. oid:
    2328053
    origin:
    Falkeidflæet ankring
    did:
    2329636
    destination:
    Stanlow
  33. oid:
    2329636
    origin:
    Stanlow
    did:
    2328123
    destination:
    Fonnesflaket ankring
  34. oid:
    2328099
    origin:
    Mongstad
    did:
    2329636
    destination:
    Stanlow
  35. oid:
    2329636
    origin:
    Stanlow
    did:
    2328099
    destination:
    Mongstad
  36. oid:
    2451822
    origin:
    Gismarvik
    did:
    2329636
    destination:
    Stanlow
  37. oid:
    2329636
    origin:
    Stanlow
    did:
    2451822
    destination:
    Gismarvik

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.