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:13 | 🚄 1N90 | Farnham → London Waterloo Up (SW → NE) | approaching |
| 07:19 | 🚆 2S09 | London Waterloo → Weybridge (B) Down (NE → SW) | -1 min |
| 07:19 | 🚄 1S14 | Weybridge (B) → London Waterloo Up (SW → NE) | +1 min |
| 07:22 | 🚆 2C14 | Reading → London Waterloo Up (SW → NE) | on time |
| 07:27 | 🚆 2C11 | London Waterloo → Reading Down (NE → SW) | +1 min |
| 07:42 | 🚄 1N92 | Farnham → London Waterloo Up (SW → NE) | on time |
On today’s timetable, Egham crossing is predicted to be closed for about 6 h 37 min between 06:00 and 22:00, across roughly 81 closures. The longest single predicted closure is 7 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: 7.0 min (06:46–06:53, 3 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 06:44–07:44 in the morning and around 12:00–13:00 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Egham is a cctv-monitored manual barrier crossing (CCTV) on the Staines–Virginia Water 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 991 trains through this crossing.
98.9% of observed passes were being warned about on this page when they passed, and 99.9% of the warnings we could verify came true.
Typical timing error was ±51s (9 in 10 within 96s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.