Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR SPD1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 11:05 | 🚆 2K12 | Peterborough → Lincoln Down (SE → NW) | passed |
| 11:10 | 🚆 2K09 | Lincoln → Peterborough Up (NW → SE) | +2 min |
| 11:23 | 🚆 2K10 | Peterborough → Lincoln Down (SE → NW) | approaching |
| 11:29 | 🚛 6E86 | Middleton Towers GBRF → Monk Bretton Redfearns GBRF Down (SE → NW) | cancelled |
On today’s timetable, Blue Gowt crossing is predicted to be closed for about 2 h 25 min between 06:00 and 22:00, across roughly 27 closures. The longest single predicted closure is 7 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: 6.1 min (11:03–11:09, 2 trains), 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 09:34–10:34 in the morning and around 14:32–15:32 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Blue Gowt is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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 377 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.2% of the warnings we could verify came true.
Typical timing error was ±13s (9 in 10 within 312s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.