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.
| 07:03 | 🚆 2F81 | Cleethorpes → Barton-on-Humber Down (E → W) | +1 min |
| 07:05 | 🚆 2J41 | Lincoln → Grimsby Town Down (E → W) | cancelled |
| 07:20 | 🚆 2A14 | Grimsby Town → Matlock Up (W → E) | active |
| 07:32 | 🚄 1B69 | Cleethorpes → Liverpool Lime Street HL/ML Down (E → W) | active |
| 07:34 | 🚄 1B62 | Sheffield → Cleethorpes Down (E → W) | approaching |
On today’s timetable, Wellowgate crossing is predicted to be closed for about 4 h 34 min between 06:00 and 22:00, across roughly 64 closures. The longest single predicted closure is 6 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 (05:10–05:13, 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:59–07:59 in the morning and around 12:40–13:40 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Wellowgate is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Cleethorpes–Great Coates 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 443 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.2% of the warnings we could verify came true.
Typical timing error was ±6s (9 in 10 within 80s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.