CCTV-monitored manual barrier level crossing on the East Coast route (ELR NOB1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:58 | 🚆 2A12 | Lincoln → Matlock Up (NE → SW) | no show |
| 08:01 | 🚄 1K57 | Newark Castle → Crewe Up (NE → SW) | active |
| 08:03 | 🚆 2N47 | Leicester → Lincoln Down (SW → NE) | approaching |
| 08:17 | 🚆 2J49 | Ambergate → Cleethorpes Down (SW → NE) | +1 min |
| 08:18 | 🚆 2D40 | Lincoln → Nottingham Up (NE → SW) | on time |
On today’s timetable, Newark Castle crossing is predicted to be closed for about 4 h 14 min between 06:00 and 22:00, across roughly 60 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 (01:56–01:59, 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:53–07:53 in the morning and around 16:07–17:07 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Newark Castle is a cctv-monitored manual barrier crossing (CCTV) on the Rolleston–Retford line (East Coast route · ELR NOB1). 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 231 trains through this crossing.
100.0% 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 ±36s (9 in 10 within 145s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.