CCTV-monitored manual barrier level crossing on the Anglia route (ELR COC).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:21 | 🚄 1N31 | Clacton-on-Sea → London Liverpool Street Up (E → W) | passed |
| 09:22 | 🚆 2F16 | Colchester → Walton-on-the-Naze Down (W → E) | passed |
| 09:30 | 🚆 2F21 | Walton-on-the-Naze → Colchester Up (E → W) | approaching |
| 09:31 | 🚄 1N12 | London Liverpool Street → Clacton-on-Sea Down (W → E) | approaching |
On today’s timetable, Thorrington crossing is predicted to be closed for about 4 h 15 min between 06:00 and 22:00, across roughly 44 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: 6.8 min (06:47–06:54, 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:38–08:38 in the morning and around 20:15–21:15 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Thorrington is a cctv-monitored manual barrier crossing (CCTV) on the Colchester Town–Thorpe-le-Soken line (Anglia route · ELR COC). 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 537 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 100.0% of the warnings we could verify came true.
Typical timing error was ±5s (9 in 10 within 80s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.