CCTV-monitored manual barrier level crossing on the Scotland route (ELR WCM2).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:52 | 🚄 1M10 | Glasgow Central High Level → London Euston Up (NW → SE) | +1 min |
| 09:56 | 🚄 9M53 | Glasgow Central High Level → London Euston Up (NW → SE) | passed |
| 10:19 | 🚄 1S35 | Manchester Airport → Glasgow Central High Level Down (SE → NW) | +1 min |
On today’s timetable, Logans Road crossing is predicted to be closed for about 4 h 45 min between 06:00 and 22:00, across roughly 59 closures. The longest single predicted closure is 8 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.2 min (07:13–07:19, 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 07:48–08:48 in the morning and around 16:03–17:03 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 Logans Road in Forgewood, North Lanarkshire.
Logans Road is a CCTV-monitored manual barrier crossing (CCTV) on the Motherwell–Uddingston line (Scotland route · ELR WCM2). 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 547 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.0% of the warnings we could verify came true.
Typical timing error was ±38s (9 in 10 within 141s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.