CCTV-monitored manual barrier level crossing on the Wessex route (ELR RDG1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:14 | 🚆 2C20 | Reading → London Waterloo Up (W → E) | -2 min |
| 09:19 | 🚆 2U19 | London Waterloo → Windsor & Eton Riverside Down (E → W) | passed |
| 09:21 | 🚆 2K13 | London Waterloo → London Waterloo Up (W → E) | passed |
| 09:25 | 🚆 2O17 | London Waterloo → London Waterloo Down (E → W) | approaching |
| 09:28 | 🚆 2U20 | Windsor & Eton Riverside → London Waterloo Up (W → E) | -1 min |
| 09:34 | 🚆 2C21 | London Waterloo → Reading Down (E → W) | on time |
| 09:45 | 🚆 2C22 | Reading → London Waterloo Up (W → E) | -1 min |
| 09:51 | 🚄 1Z21 | London Waterloo → Bracknell Down (E → W) | active |
| 09:52 | 🚆 2K15 | London Waterloo → London Waterloo Up (W → E) | on time |
| 09:54 | 🚆 2O19 | London Waterloo → London Waterloo Down (E → W) | active |
On today’s timetable, Mortlake crossing is predicted to be closed for about 10 h 37 min between 06:00 and 22:00, across roughly 118 closures. The longest single predicted closure is 11 minutes. Freight paths scheduled “as required” (most don’t run on any given day) aren’t counted here; when one does run, the live timeline above shows it.
Longest closure so far today: 12.9 min (00:12–00:25, 5 trains), timed from trains actually seen on the signalling wire: the window edges use the same per-type margins as the forecast, since barrier positions aren't in any feed we can read.
Closures cluster around 08:08–09:08 in the morning and around 18:56–19:56 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Sheen Lane in Mortlake, London, next to the station.
Mortlake is a CCTV-monitored manual barrier crossing (CCTV) on the Barnes–Richmond line (Wessex route · ELR RDG1). A signaller monitors the crossing, confirms it is clear, and lowers the barriers ahead of each train. Forecasts here combine the working timetable with live train-movement data (and live signalling where the crossing has it), so they reflect actual running including delays and freight, though they can still be wrong when the network is disrupted.
We score this page against what actually happened on the railway: over the last 7 days that covered 1,785 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.7% of the warnings we could verify came true.
Typical timing error was ±32s (9 in 10 within 95s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.