Harry Moor Lane level crossing

User-worked with stop lights level crossing on the North and East route (ELR HUL3).

predicted
OPEN
for 21 min

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

next: 🚃 in 22 min · 14 min early

Next 30 min

OPEN 04:56–05:17 21m
CLOSED 05:17–05:18 50s
OPEN 05:18–05:42 → 24m
Under the hood
Mon 07 Sep · 04:56
Today Tomorrow

Trains in window

05:18 🚃 3K03 Holbeck Loco SidingsSelby Down (W → E) -14 min
🚃Empty stock
now 04:56:39 · 125 avg · 1 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,725 active · 21,573 delays · 2,956 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Harry Moor Lane crossing is predicted to be closed for about 2 h 35 min between 06:00 and 22:00, across roughly 99 closures. The longest single predicted closure is 2 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:25–07:25 in the morning and around 12:45–13:45 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

Harry Moor Lane is a user-worked with stop lights crossing (UWCMSL) on the Micklefield–Selby line (North and East route · ELR HUL3). 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 360 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 ±87s (9 in 10 within 187s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?