Ebley level crossing

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

predicted
OPEN
for 2 min

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

next: 🚄 in 3 min · 9 min late

Next 30 min

OPEN 09:58–10:00 2m
CLOSED 10:00–10:01 50s
OPEN 10:01–10:28 → 27m
Under the hood
Thu 22 Oct · 09:58
Today Tomorrow

Trains in window

10:01 🚄 1G07 London Paddington → Cheltenham Spa Down (E → W) approaching
10:25 🚛 6B34 Bicester MOD GBRf → Ashchurch MOD GBRf Down (E → W) no show
🚄Express passenger 🚛Freight
now 09:58:14 · 46 avg · 2 in window
live observation: 1 up · 2 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active · 31,697 delays · 1,962 cancelled · 9 reconnects
About this crossing

How often it closes

On today’s timetable, Ebley crossing is predicted to be closed for about 1 h 2 min between 06:00 and 22:00, across roughly 33 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: 2.1 min (08:23–08:25, 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 06:19–07:19 in the morning and around 16:27–17:27 in the afternoon. 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 Chapel Lane in Ebley, Gloucestershire.

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 259 trains through this crossing.

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

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

Full accuracy report →

Is this right?