Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR NOB1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 16:52 | 🚆 2A30 | Lincoln → Matlock Down (SW → NE) | +2 min |
| 16:54 | 🚄 1N66 | Crewe → Lincoln Up (NE → SW) | on time |
| 17:12 | 🚆 2N67 | Matlock → Lincoln Up (NE → SW) | on time |
| 17:16 | 🚄 1K75 | Lincoln → Crewe Down (SW → NE) | +2 min |
On today’s timetable, Rolleston Station crossing is predicted to be closed for about 4 h 23 min between 06:00 and 22:00, across roughly 61 closures. The longest single predicted closure is 6 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.6 min (08:50–08:57, 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 08:45–09:45 in the morning and around 12:14–13:14 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Rolleston Station is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Nottingham–Rolleston line (East Midlands route · ELR NOB1). 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 471 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.4% of the warnings we could verify came true.
Typical timing error was ±91s (9 in 10 within 118s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.