CCTV-monitored manual barrier level crossing on the Sussex route (ELR BLI1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:56 | 🚄 1N13 | Southampton Central → Brighton Up (W → E) | passed |
| 09:58 | 🚄 1H12 | London Victoria (C) → Littlehampton Down (E → W) | passed |
| 10:01 | 🚄 1N20 | Brighton → Southampton Central Down (E → W) | approaching |
| 10:07 | 🚆 2Y20 | Brighton → Chichester Down (E → W) | -1 min |
| 10:08 | 🚄 1S17 | Portsmouth & Southsea → Brighton Up (W → E) | approaching |
| 10:15 | 🚄 1H21 | Littlehampton → London Victoria (C) Up (W → E) | on time |
| 10:20 | 🚄 1N22 | Brighton → Southampton Central Down (E → W) | active |
| 10:26 | 🚄 1N15 | Southampton Central → Brighton Up (W → E) | +1 min |
On today’s timetable, Portslade crossing is predicted to be closed for about 11 h 25 min between 06:00 and 22:00, across roughly 129 closures. The longest single predicted closure is 9 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: 21.9 min (07:37–07:58, 9 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 18:03–19:03 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Station Road / Boundary Road in Portslade by Sea, East Sussex, next to Portslade station.
Portslade is a CCTV-monitored manual barrier crossing (CCTV) on the Hove–Shoreham-by-Sea 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,431 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.0% of the warnings we could verify came true.
Typical timing error was ±11s (9 in 10 within 61s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.