Tranmere

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T08:43:13Z.

Havn

havn_id:
2329664
navn:
Tranmere
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
53.3666666666667
lon:
-3.01666666666667

Port-call and departure connections

38 results

  1. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  2. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  3. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  4. oid:
    2329664
    origin:
    Tranmere
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  5. oid:
    2329664
    origin:
    Tranmere
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  6. oid:
    2329664
    origin:
    Tranmere
    did:
    2447771
    destination:
    Tromsø ankring
  7. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  8. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  9. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  10. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  11. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  12. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  13. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  14. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  15. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  16. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  17. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  18. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  19. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  20. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  21. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  22. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  23. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  24. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  25. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  26. oid:
    2328099
    origin:
    Mongstad
    did:
    2329664
    destination:
    Tranmere
  27. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  28. oid:
    2329664
    origin:
    Tranmere
    did:
    2328099
    destination:
    Mongstad
  29. oid:
    2329664
    origin:
    Tranmere
    did:
    2451779
    destination:
    Karlsmedgrunnen ankring
  30. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  31. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  32. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  33. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  34. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  35. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  36. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture
  37. oid:
    2328120
    origin:
    Sture
    did:
    2329664
    destination:
    Tranmere
  38. oid:
    2329664
    origin:
    Tranmere
    did:
    2328120
    destination:
    Sture

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.