CCTV-monitored manual barrier level crossing on the Sussex route (ELR BLI1).
| 00:08 | 1H92 | 🚄 | VICTRIC → BOGNORR | ← from Worthing | +23 min |
| 00:13 | 2T92 | 🚆 | BRGHTN → WWRTHNG | ← from Worthing | +4 min |
| 00:14 | 5T93 | 🚃 | WWRTHNG → LOVRSWS | → from Angmering | approaching |
| 00:16 | 2S95 | 🚆 | PHBR → BRGHTN | → from Angmering | approaching |
| 00:26 | 3S97 | 🚧 | HORSHUS → HORSHUS | → from Angmering | no show |
| 00:39 | 2T94 | 🚆 | BRGHTN → WWRTHNG | ← from Worthing | on time |
On today’s timetable, West Worthing crossing is predicted to be closed for about 11 h 19 min between 06:00 and 22:00, across roughly 108 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: 9.4 min (00:04–00:13, 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 07:16–08:16 in the morning and around 12:18–13:18 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
West Worthing is a cctv-monitored manual barrier crossing (CCTV) on the Worthing–Angmering line (Sussex route · ELR BLI1). 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 704 trains through this crossing.
98.7% of observed passes were being warned about on this page when they passed, and 99.8% of the warnings we could verify came true.
Typical timing error was ±32s (9 in 10 within 74s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.