Red Lane (mgh) level crossing

Manual gate level crossing on the North and East route (ELR WAG1).

predicted
OPEN
for at least 2h

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

Next 30 min

OPEN 02:12–04:12+ 2h+
Under the hood
Mon 07 Sep · 02:12
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:12:27 · 53 avg · 0 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,283 active · 21,045 delays · 2,871 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Red Lane (mgh) crossing is predicted to be closed for about 2 h 41 min between 06:00 and 22:00, across roughly 32 closures. The longest single predicted closure is 5 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 07:19–08:19 in the morning and around 12:33–13:33 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

Red Lane (mgh) is a manual gate crossing (MGH) on the Wakefield Kirkgate–Knottingley line (North and East route · ELR WAG1). A signaller or crossing keeper closes the gates across the road 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 359 trains through this crossing.

100.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 ±5s (9 in 10 within 54s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?