Gringley Road (mcbr) level crossing

Remotely-monitored manually-controlled barrier level crossing on the North and East route (ELR MAC3).

predicted
CLOSED
for 2 min

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

next: 🚄 in 1 min · on time

Next 30 min

CLOSED 07:52–07:54 2m
OPEN 07:54–08:22 28m
CLOSED 08:22–08:25 → 3m
Under the hood
Mon 12 Oct · 07:52
Today Tomorrow

Trains in window

07:53 🚄 1L40 Lincoln → Leeds Down (NE → SW) approaching
08:25 🚄 1L33 Leeds → Lincoln Up (SW → NE) +5 min
🚄Express passenger
now 07:52:27 · 34 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-11..2026-10-13
fetched 02:08:22
trust 48,888 active · 26,187 delays · 2,581 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Gringley Road (mcbr) crossing is predicted to be closed for about 2 h 22 min between 06:00 and 22:00, across roughly 35 closures. The longest single predicted closure is 3 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: 3.2 min (06:05–06:08, 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:20–07:20 in the morning and around 13:34–14:34 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

The crossing is on Grove Lane in Retford, Nottinghamshire.

Gringley Road (mcbr) is a remotely-monitored manually-controlled barrier crossing (MCBR) on the Lincoln–Worksop line (North and East route · ELR MAC3). 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 255 trains through this crossing.

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

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

Full accuracy report →

Is this right?