Pevensey Sluice level crossing

Automatic half-barrier level crossing on the Sussex route (ELR WJB).

predicted
OPEN
for 11 min

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

next: 🚆 in 12 min · 1 min early

Next 30 min

OPEN 17:53–18:03 11m
CLOSED 18:03–18:05 2m
OPEN 18:05–18:13 8m
CLOSED 18:13–18:14 1m
OPEN 18:14–18:17 3m
CLOSED 18:17–18:19 2m
OPEN 18:19–18:31 → 13m
Under the hood
Thu 08 Oct · 17:53
Today Tomorrow

Trains in window

17:45 🚄 1F53 Ore → London Victoria (C) Up (E → W) +1 min
18:04 🚆 2D54 Eastbourne → Ashford International Down (W → E) approaching
18:13 🚄 1U51 Ore → Brighton Up (E → W) active
18:18 🚄 1U54 Brighton → Ore Down (W → E) -1 min
🚄Express passenger 🚆Passenger
now 17:53:08 · 130 avg · 4 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-07..2026-10-09
fetched 02:08:26
trust 33,690 active · 32,059 delays · 2,197 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Pevensey Sluice crossing is predicted to be closed for about 3 h 32 min between 06:00 and 22:00, across roughly 93 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: 3.9 min (15:38–15:42, 2 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 07:38–08:38 in the morning and around 19:11–20:11 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Pevensey Sluice is a automatic half-barrier crossing (AHB) on the Normans Bay–Hastings line (Sussex route · ELR WJB). The approaching train itself triggers the closure at a fixed point on its approach. 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 745 trains through this crossing.

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

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

Full accuracy report →

Is this right?