CCTV-monitored manual barrier level crossing on the East Midlands route (ELR SPD1).
| 02:02 | 4L39 | 🚛 | NORMGBF → TLBYTCG | → from Sleaford | -10 min |
| 02:08 | 4L73 | 🚛 | MBROSTY → FLXSNEW | → from Sleaford | -40 min |
| 02:14 | 4E46 | 🚛 | FLXSNEW → NORMPW | ← from Peterborough North Yd GBRf | -22 min |
| 02:20 | 6E04 | 🚧 | WHTMLDC → DONCUDY | ← from Peterborough North Yd GBRf | -44 min |
| 02:36 | 4E45 | 🚛 | FLXSSEW → NORMPW | ← from Peterborough North Yd GBRf | no show |
On today’s timetable, Winsover Road crossing is predicted to be closed for about 2 h 5 min between 06:00 and 22:00, across roughly 23 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: 3.2 min (00:20–00:23, 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 16:51–17:51 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Winsover Road is a cctv-monitored manual barrier crossing (CCTV) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 1 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 ±179s (9 in 10 within 179s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.