CCTV-monitored manual barrier level crossing on the Anglia route (ELR TLL).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 08:05 | 🚆 2R73 | Pitsea → London Fenchurch Street Up (NE → SW) | passed |
| 08:11 | 🚆 2R66 | London Fenchurch Street → Pitsea Down (SW → NE) | approaching |
| 08:27 | 🚄 1D12 | London Fenchurch Street → Pitsea Down (SW → NE) | +2 min |
| 08:29 | 🚛 4L31 | Daventry Int RFT Recep FL → London Gateway Frghtliner Down (SW → NE) | no show |
| 08:34 | 🚆 2R77 | Pitsea → London Fenchurch Street Up (NE → SW) | active |
On today’s timetable, Low Street crossing is predicted to be closed for about 5 h between 06:00 and 22:00, across roughly 75 closures. The longest single predicted closure is 6 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.5 min (00:10–00:16, 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 07:04–08:04 in the morning and around 18:33–19:33 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Low Street is a cctv-monitored manual barrier crossing (CCTV) on the Tilbury Town–Pitsea line (Anglia route · ELR TLL). 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 878 trains through this crossing.
99.9% of observed passes were being warned about on this page when they passed, and 98.4% of the warnings we could verify came true.
Typical timing error was ±9s (9 in 10 within 24s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.