Automatic half-barrier level crossing on the East Midlands route (ELR NOB1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:03 | 🚆 2T52 | Cleethorpes → Newark North Gate Up (E → W) | on time |
| 07:17 | 🚆 2A12 | Lincoln → Matlock Up (E → W) | approaching |
| 07:21 | 🚆 2N45 | Nottingham → Lincoln Down (W → E) | -1 min |
| 07:37 | 🚛 6E46 | Kingsbury Oil Sdgs → Humber Oil Refinery Down (W → E) | no show |
| 07:39 | 🚄 1B81 | Lincoln → London Kings Cross Up (E → W) | active |
On today’s timetable, EAGLE and crossing is predicted to be closed for about 3 h 15 min between 06:00 and 22:00, across roughly 68 closures. The longest single predicted closure is 4 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: 2.0 min (06:12–06:14, 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 06:48–07:48 in the morning and around 15:27–16:27 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
EAGLE and is a automatic half-barrier crossing (AHB-X) on the Down–Worksop line (East Midlands route · ELR NOB1). The approaching train itself triggers the closure at a fixed point on its approach. 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 577 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.6% of the warnings we could verify came true.
Typical timing error was ±34s (9 in 10 within 642s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.