CCTV-monitored manual barrier level crossing on the East Coast route (ELR ECM1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:58 | 🚄 1D07 | London Kings Cross → Leeds Down (S → N) | passed |
| 10:01 | 🚄 1E04 | Edinburgh → London Kings Cross Up (N → S) | approaching |
| 10:02 | 🚛 4D30 | P'bro Westwood Sdgs GBRf → Doncaster Down Decoy GBRF Down (S → N) | no show |
| 10:04 | 🚄 1A92 | Beverley → London Kings Cross Up (N → S) | +8 min |
| 10:10 | 🚄 1Y09 | Newcastle → London Kings Cross Up (N → S) | +3 min |
| 10:12 | 🚄 1A13 | Harrogate → London Kings Cross Up (N → S) | +13 min |
| 10:31 | 🚄 1S09 | London Kings Cross → Aberdeen Down (S → N) | +8 min |
| 10:31 | 🚄 1A14 | Leeds → London Kings Cross Up (N → S) | +1 min |
| 10:33 | 🚄 1A70 | Bradford Interchange → London Kings Cross Up (N → S) | +7 min |
| 10:33 | 🚄 1H02 | London Kings Cross → Hull Down (S → N) | -1 min |
On today’s timetable, Cromwell Lane crossing is predicted to be closed for about 11 h 4 min between 06:00 and 22:00, across roughly 111 closures. The longest single predicted closure is 16 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: 12.4 min (08:25–08:37, 5 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 08:17–09:17 in the morning and around 12:17–13:17 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Norwell Lane in Cromwell, Nottinghamshire.
Cromwell Lane is a CCTV-monitored manual barrier crossing (CCTV) on the Newark North Gate–Retford line (East Coast route · ELR ECM1). 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,369 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.