Beach Road level crossing

CCTV-monitored manual barrier level crossing on the Sussex route (ELR STS).

predicted
OPEN
for 4 min

Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.

next: 🚆 in 7 min · 1 min early

Next 30 min

OPEN 08:04–08:09 4m
CLOSED 08:09–08:12 3m
OPEN 08:12–08:25 13m
CLOSED 08:25–08:28 3m
OPEN 08:28–08:39 → 11m
Under the hood
Tue 06 Oct · 08:04
Today Tomorrow

Trains in window

07:57 🚆 2C13 Seaford → Brighton Up (SE → NW) on time
08:12 🚆 2C10 Brighton → Seaford Down (NW → SE) -1 min
08:28 🚆 2C15 Seaford → Brighton Up (SE → NW) active
🚆Passenger
now 08:04:56 · 86 avg · 3 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-05..2026-10-07
fetched 02:08:18
trust 33,462 active · 31,746 delays · 1,716 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Beach Road crossing is predicted to be closed for about 4 h 28 min between 06:00 and 22:00, across roughly 62 closures. The longest single predicted closure is 3 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.7 min (05:24–05:31, 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.

Worst times to cross today

Closures cluster around 09:39–10:39 in the morning and around 18:54–19:54 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Beach Road is a cctv-monitored manual barrier crossing (CCTV) on the Lewes–Newhaven Marine Ag Tml DBC line (Sussex route · ELR STS). 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.

How accurate is this forecast?

We score this page against what actually happened on the railway — over the last 7 days that covered 713 trains through this crossing.

99.3% of observed passes were being warned about on this page when they passed, and 98.8% of the warnings we could verify came true.

Typical timing error was ±86s (9 in 10 within 840s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?