Ebley level crossing

User-worked with stop lights level crossing on the Western route (ELR SWM1).

right now
OPEN
for at least 2h

Next 30 min

OPEN 01:09–03:09+ 2h+
Under the hood
Fri 24 Jul · 01:09
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:09:39 · 49 avg · 0 in window
lx berths down: GL/DK01→GL/[email protected] · down: GL/DK98→GL/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,084 active · 30,121 delays · 1,790 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Ebley crossing is predicted to be closed for about 58 min between 06:00 and 22:00, across roughly 36 closures. The longest single predicted closure is 1 minute. 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: 0.6 min (00:52–00:52, 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 06:23–07:23 in the morning and around 12:54–13:54 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Ebley is a user-worked with stop lights crossing (UWCMSL) on the Stroud–Westerleigh Puma DBC line (Western route · ELR SWM1). 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 124 trains through this crossing.

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

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

Full accuracy report →

Is this right?