Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR MAC3).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 06:36 | 🚄 1B67 | Cleethorpes → Liverpool Lime Street HL/ML Down (SE → NW) | +1 min |
| 06:55 | 🚆 2J41 | Lincoln → Grimsby Town Up (NW → SE) | approaching |
| 07:11 | 🚆 2F81 | Cleethorpes → Barton-on-Humber Down (SE → NW) | active |
On today’s timetable, Stallingborough crossing is predicted to be closed for about 4 h 23 min between 06:00 and 22:00, across roughly 46 closures. The longest single predicted closure is 9 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: 4.5 min (03:16–03:20, 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.
Closures cluster around 06:48–07:48 in the morning and around 17:47–18:47 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Stallingborough is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Cleethorpes–Barton-on-Humber line (North and East route · ELR MAC3). 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 464 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.8% of the warnings we could verify came true.
Typical timing error was ±3s (9 in 10 within 222s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.