Cooksbridge level crossing

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

predicted
CLOSED
for 3 min

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

next: 🚛 in 3 min · 25 min early

Next 30 min

CLOSED 04:55–04:58 3m
MAY OPEN 04:58–05:00 2m
CLOSED 05:00–05:05 5m
OPEN 05:05–05:13 8m
CLOSED 05:13–05:16 3m
OPEN 05:16–05:27 → 11m
Under the hood
Mon 07 Sep · 04:55
Today Tomorrow

Trains in window

04:58 🚛 6O12 Hanwell Bridge LoopNewhaven Day Aggs Down (NW → SE) approaching
05:04 🚛 6O90 Acton T.C.Newhaven Marine Ag Tml DBC Down (NW → SE) -20 min
05:16 🚄 1F01 EastbourneLondon Victoria (C) Up (SE → NW) +1 min
🚄Express passenger 🚛Freight
now 04:55:11 · 70 avg · 3 in window
live observation: 0 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,718 active · 21,554 delays · 2,954 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Cooksbridge crossing is predicted to be closed for about 4 h 18 min between 06:00 and 22:00, across roughly 61 closures. The longest single predicted closure is 6 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: 3.2 min (23:58–00:01, 1 train), 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 07:27–08:27 in the morning and around 17:22–18:22 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Cooksbridge is a cctv-monitored manual barrier crossing (CCTV) on the Plumpton–Lewes line (Sussex route · ELR KJE1). 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 192 trains through this crossing.

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

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

Full accuracy report →

Is this right?