Manual barrier level crossing on the Scotland route (ELR WCM1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:51 | 🚄 1M84 | Glasgow Central High Level → Manchester Airport Up (W → E) | on time |
| 09:52 | 🚄 1S35 | Manchester Airport → Glasgow Central High Level Down (E → W) | +1 min |
| 09:55 | 🚄 1S37 | London Euston → Glasgow Central High Level Down (E → W) | passed |
| 10:00 | 🚄 1M01 | Stirling → London Euston Up (W → E) | approaching |
| 10:17 | 🚄 1M10 | Glasgow Central High Level → London Euston Up (W → E) | +1 min |
| 10:17 | 🚛 4M06 | Mossend Euroterminal → East Mids Gateway Tml DBC Up (W → E) | no show |
| 10:17 | 🚛 4E74 | Mossend Down Yard → Masborough F.D. Up (W → E) | no show |
| 10:24 | 🚄 1S00 | London Euston → Stirling Down (E → W) | approaching |
| 10:24 | 🚄 9M53 | Glasgow Central High Level → London Euston Up (W → E) | +4 min |
| 10:25 | 🚧 3S93 | Alloa → Carstairs C.E. Up (W → E) | -2 min |
On today’s timetable, Bodsbury crossing is predicted to be closed for about 6 h 11 min between 06:00 and 22:00, across roughly 87 closures. The longest single predicted closure is 10 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: 7.5 min (09:47–09:55, 3 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 09:48–10:48 in the morning and around 14:09–15:09 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is near Elvanfoot, South Lanarkshire.
Bodsbury is a manual barrier crossing (MBWM) on the Carlisle Network Yard–Abington line (Scotland route · ELR WCM1). 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 809 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 ±3s (9 in 10 within 10s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.