Plumpton level crossing

Manually-controlled barrier with obstacle detection level crossing on the Sussex route (ELR KJE1).

right now
OPEN
for 4 min
next: 🚄 in 7 min · 1 min early

Next 30 min

OPEN 01:11–01:14 4m
CLOSED 01:14–01:17 3m
OPEN 01:17–03:11+ 1h+
Under the hood
Fri 24 Jul · 01:11
Today Tomorrow

Trains in window

01:17 1F72 🚄 HYWRDSH → EBOURNE ← from Plumpton -1 min
🚄Express passenger
now 01:11:08 · 94 avg · 1 in window
lx berths up: TB/0642→TB/[email protected] · up: TB/0648→TB/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,793 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Plumpton crossing is predicted to be closed for about 4 h 8 min between 06:00 and 22:00, across roughly 61 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: 7.4 min (00:36–00:43, 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:31–08:31 in the morning and around 20:05–21:05 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Plumpton is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Plumpton–Lewes line (Sussex route · ELR KJE1). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 239 trains through this crossing.

100.0% 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 ±336s (9 in 10 within 452s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?