CCTV-monitored manual barrier level crossing on the Sussex route (ELR BLI1).
| 00:19 | 2T94 | 🚆 | BRGHTN → WWRTHNG | ← from Hove | approaching |
| 00:29 | 1H96 | 🚄 | VICTRIC → WORTHNG | ← from Hove | no show |
| 00:31 | 5T93 | 🚃 | WWRTHNG → LOVRSWS | → from Southwick | active |
| 00:35 | 5H95 | 🚃 | WORTHNG → LOVRSWS | → from Southwick | active |
| 00:35 | 2S95 | 🚆 | PHBR → BRGHTN | → from Southwick | +11 min |
| 00:41 | 3S97 | 🚧 | HORSHUS → HORSHUS | → from Southwick | no show |
On today’s timetable, Portslade crossing is predicted to be closed for about 10 h 34 min between 06:00 and 22:00, across roughly 109 closures. The longest single predicted closure is 14 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.2 min (23:57–00:03, 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:19–08:19 in the morning and around 13:03–14:03 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Portslade is a cctv-monitored manual barrier crossing (CCTV) on the Hove–Southwick 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 1,408 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.1% of the warnings we could verify came true.
Typical timing error was ±43s (9 in 10 within 99s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.