Battle Marley Lane level crossing

CCTV-monitored manual barrier level crossing on the Kent route (ELR TTH).

predicted
CLOSED
for 3 min

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

next: 🚄 now · on time

Next 30 min

CLOSED 10:00–10:03 3m
OPEN 10:03–10:39 → 36m
Under the hood
Thu 22 Oct · 10:00
Today Tomorrow

Trains in window

10:00 🚄 1H72 Hastings → London Charing Cross Up (S → N) approaching
10:03 🚄 1H16 London Charing Cross → Hastings Down (N → S) approaching
🚄Express passenger
now 10:00:51 · 82 avg · 2 in window
live observation: 2 up · 2 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,174 active · 31,699 delays · 1,966 cancelled · 9 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Battle Marley Lane crossing is predicted to be closed for about 4 h 16 min between 06:00 and 22:00, across roughly 60 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: 6.8 min (07:30–07:37, 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 06:34–07:34 in the morning and around 18:50–19:50 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

The crossing is on Marley Lane in Battle, East Sussex, next to the station.

Battle Marley Lane is a CCTV-monitored manual barrier crossing (CCTV) on the Robertsbridge–Battle line (Kent route · ELR TTH). 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 513 trains through this crossing.

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

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

Full accuracy report →

Is this right?