CCTV-monitored manual barrier level crossing on the East Midlands route (ELR SPC6).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:53 | 🚄 1N54 | Crewe → Lincoln Up (NW → SE) | passed |
| 10:11 | 🚄 1F17 | London St. Pancras → Sheffield Up (NW → SE) | +9 min |
| 10:12 | 🚄 1K59 | Lincoln → Crewe Up (NW → SE) | on time |
| 10:28 | 🚄 1V07 | Nottingham → Cardiff Central Up (NW → SE) | active |
| 10:29 | 🚆 2N55 | Matlock → Lincoln Up (NW → SE) | on time |
On today’s timetable, Sawley crossing is predicted to be closed for about 9 h 1 min between 06:00 and 22:00, across roughly 111 closures. The longest single predicted closure is 9 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: 13.8 min (08:26–08:40, 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 07:16–08:16 in the morning and around 16:30–17:30 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Sawley Road in Breaston, Derbyshire.
Sawley is a CCTV-monitored manual barrier crossing (CCTV) on the Down–Derby line (East Midlands route · ELR SPC6). 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,449 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.7% of the warnings we could verify came true.
Typical timing error was ±5s (9 in 10 within 10s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.