Keymer level crossing

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

right now
CLOSED
for 3 min
next: 🚄 now · scheduled

Next 30 min

CLOSED 00:13–00:17 3m
OPEN 00:17–00:24 8m
CLOSED 00:24–00:27 3m
OPEN 00:27–00:31 4m
CLOSED 00:31–00:34 3m
OPEN 00:34–00:41 7m
CLOSED 00:41–00:45 → 3m
Under the hood
Fri 24 Jul · 00:13
Today Tomorrow

Trains in window

00:11 6Y20 🚛 NEWHVMD → CRAWRMC → from Plumpton no show
00:11 9S69 🚄 CAMBDGE → BRGHTN ← from Haywards Heath +1 min
00:14 1H96 🚄 VICTRIC → WORTHNG ← from Haywards Heath approaching
00:16 9W00 🚄 BRGHTN → BEDFDM → from Plumpton on time
00:27 1A66 🚄 VICTRIC → BRGHTN ← from Haywards Heath +6 min
00:34 8Y93 🚧 PRSP → HORSHUS → from Plumpton sched
00:44 9R69 🚄 BEDFDM → BRGHTN ← from Haywards Heath on time
🚄Express passenger 🚛Freight 🚧Engineering
now 00:13:46 · 395 avg · 7 in window
lx berths up: TB/0368→TB/[email protected] · up: TB/0642→TB/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,034 active · 29,995 delays · 1,736 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Keymer crossing is predicted to be closed for about 13 h 2 min between 06:00 and 22:00, across roughly 76 closures. The longest single predicted closure is 28 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.

Worst times to cross today

Closures cluster around 06:06–07:06 in the morning and around 17:31–18:31 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Keymer is a cctv-monitored manual barrier crossing (CCTV) on the Haywards Heath–Plumpton 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 1,136 trains through this crossing.

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

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

Full accuracy report →

Is this right?