CCTV-monitored manual barrier level crossing on the Wessex route (ELR RDG1).
| 00:05 | 2C79 | 🚆 | WATRLMN → RDNG4AB | ← from Barnes | on time |
| 00:06 | 2O60 | 🚆 | UPMNLT → UPMNLT | ← from Barnes | +1 min |
| 00:08 | 5C77 | 🚃 | WATRLMN → FELTDEP | ← from Barnes | on time |
| 00:09 | 5N31 | 🚃 | RICHNLL → WMBYLCS | → from Twickenham | +2 min |
| 00:13 | 2N32 | 🚆 | STFD → RICHNLL | ← from Barnes | +1 min |
| 00:15 | 2C80 | 🚆 | RDNG4AB → WATRLMN | → from Twickenham | -1 min |
| 00:21 | 2O13 | 🚆 | TOWERHL → KNSGHST | ← from Barnes | +9 min |
| 00:23 | 2O02 | 🚆 | TOWERHL → KNSGHST | ← from Barnes | active |
| 00:24 | 2O14 | 🚆 | UPMNLT → HAMDLUL | ← from Barnes | approaching |
| 00:26 | 2U79 | 🚆 | WATRLMN → STAINES | ← from Barnes | +3 min |
| 00:27 | 2O77 | 🚆 | WATRLMN → STRWBYH | ← from Barnes | on time |
| 00:32 | 2O06 | 🚆 | UPMNLT → RICHNLL | ← from Barnes | active |
| 00:42 | 5O06 | 🚃 | RICHNLL → LILBDGE | → from Twickenham | active |
| 00:43 | 2I15 | 🚆 | UPMNLT → KNSGHST | ← from Barnes | active |
On today’s timetable, North Sheen crossing is predicted to be closed for about 14 h 11 min between 06:00 and 22:00, across roughly 63 closures. The longest single predicted closure is 57 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: 6.6 min (00:03–00:09, 2 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:31–07:31 in the morning and around 17:56–18:56 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
North Sheen is a cctv-monitored manual barrier crossing (CCTV) on the Barnes–Twickenham 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 2,110 trains through this crossing.
99.8% of observed passes were being warned about on this page when they passed, and 99.4% of the warnings we could verify came true.
Typical timing error was ±21s (9 in 10 within 931s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.