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.
| 07:52 | 🚄 1S82 | Brighton → Portsmouth Harbour Down (E → W) | passed |
| 08:01 | 🚆 2Y96 | Brighton → Littlehampton Down (E → W) | approaching |
| 08:02 | 🚄 1N05 | Southampton Central → Brighton Up (W → E) | approaching |
| 08:08 | 🚆 2E12 | Brighton → Bognor Regis Down (E → W) | active |
| 08:12 | 🚆 2Y11 | Littlehampton → Brighton Up (W → E) | +2 min |
| 08:15 | 🚄 1H13 | Littlehampton → London Victoria (C) Up (W → E) | on time |
| 08:20 | 🚛 6O40 | Westbury Tarmac → Ardingly Hanson Aggregates Up (W → E) | no show |
| 08:20 | 🚄 1N14 | Brighton → Southampton Central Down (E → W) | active |
| 08:27 | 🚃 5H20 | Lovers Walk T&R.S.M.D → Littlehampton Down (E → W) | active |
| 08:28 | 🚄 1S07 | Portsmouth Harbour → Brighton Up (W → E) | +1 min |
On today’s timetable, Portslade crossing is predicted to be closed for about 11 h 4 min between 06:00 and 22:00, across roughly 125 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: 7.3 min (07:39–07:46, 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:19–08:19 in the morning and around 13:29–14:29 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–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,347 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 97.7% of the warnings we could verify came true.
Typical timing error was ±11s (9 in 10 within 66s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.