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.
| 10:25 | 🚄 1H12 | London Bridge (C) → Littlehampton Down (E → W) | -1 min |
| 10:34 | 🚄 1N17 | Southampton Central → Brighton Up (W → E) | passed |
| 10:40 | 🚧 3S93 | Horsham Up T.C. → Horsham Up T.C. Up (W → E) | approaching |
| 10:40 | 🚄 1S09 | Portsmouth & Southsea → Brighton Up (W → E) | +5 min |
| 10:42 | 🚆 2Y22 | Brighton → Chichester Down (E → W) | +1 min |
| 10:45 | 🚄 1N22 | Brighton → Southampton Central Down (E → W) | -1 min |
| 10:47 | 🚄 1H25 | Littlehampton → London Bridge (C) Up (W → E) | active |
| 10:56 | 🚄 1H14 | London Bridge (C) → Littlehampton Down (E → W) | on time |
| 11:04 | 🚆 2Y25 | Chichester → Brighton Up (W → E) | -1 min |
On today’s timetable, Lyminster crossing is predicted to be closed for about 10 h 35 min between 06:00 and 22:00, across roughly 144 closures. The longest single predicted closure is 10 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: 10.1 min (06:40–06:50, 4 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:57–08:57 in the morning and around 14:00–15:00 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Lyminster Road in Hampton Park, West Sussex.
Lyminster is a CCTV-monitored manual barrier crossing (CCTV) on the Arundel–Littlehampton 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,342 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.5% of the warnings we could verify came true.
Typical timing error was ±47s (9 in 10 within 60s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.