Bingham level crossing

Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR NOG1).

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:35 · 71 avg · 0 in window
lx berths down: NM/4167→NM/[email protected] · up: NM/4166→NM/[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
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Bingham crossing is predicted to be closed for about 4 h between 06:00 and 22:00, across roughly 55 closures. The longest single predicted closure is 10 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 08:19–09:19 in the morning and around 16:17–17:17 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Bingham is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Grantham–Radcliffe (Notts) line (East Midlands route · ELR NOG1). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 435 trains through this crossing.

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

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

Full accuracy report →

Is this right?