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.
| 07:05 | 🚆 2C11 | London Waterloo → Reading Down (E → W) | +1 min |
| 07:07 | 🚆 2V05 | Hounslow → London Waterloo Up (W → E) | +1 min |
| 07:08 | 🚆 2H89 | London Waterloo → Shepperton Down (E → W) | passed |
| 07:19 | 🚆 2C12 | Reading → London Waterloo Up (W → E) | +2 min |
| 07:20 | 🚆 2U11 | London Waterloo → Windsor & Eton Riverside Down (E → W) | -1 min |
| 07:24 | 🚆 2K05 | London Waterloo → London Waterloo Up (W → E) | on time |
| 07:24 | 🚆 2O09 | London Waterloo → London Waterloo Down (E → W) | on time |
| 07:32 | 🚆 2U12 | Windsor & Eton Riverside → London Waterloo Up (W → E) | on time |
| 07:34 | 🚆 2C13 | London Waterloo → Reading Down (E → W) | active |
| 07:36 | 🚆 2H92 | Shepperton → London Waterloo Up (W → E) | -1 min |
| 07:38 | 🚆 2R09 | London Waterloo → London Waterloo Down (E → W) | active |
| 07:42 | 🚄 1N90 | Farnham → London Waterloo Up (W → E) | +2 min |
On today’s timetable, Mortlake crossing is predicted to be closed for about 12 h 12 min between 06:00 and 22:00, across roughly 117 closures. The longest single predicted closure is 13 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: 8.8 min (06:21–06:30, 4 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 09:28–10:28 in the morning and around 17:13–18:13 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
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,713 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.6% of the warnings we could verify came true.
Typical timing error was ±7s (9 in 10 within 91s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.