Manually-controlled barrier level crossing on the Western route (ELR BAG2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 17:51 | 🚄 1V62 | Edinburgh → Plymouth Down (N → S) | on time |
| 18:01 | 🚄 1M75 | Cardiff Central → Nottingham Up (S → N) | +1 min |
| 18:06 | 🚆 2E70 | Bristol Temple Meads → Worcester Foregate Street Up (S → N) | +15 min |
| 18:11 | 🚛 6V30 | Handsworth Queens Head Sdgs → Alexandra Dock Jn. T.C. Down (N → S) | no reports |
| 18:13 | 🚄 1E63 | Plymouth → Newcastle Up (S → N) | on time |
| 18:17 | 🚛 6M53 | Swindon Stores → Toton Up Sdgs Up (S → N) | cancelled |
| 18:18 | 🚄 1V13 | Nottingham → Cardiff Central Down (N → S) | +1 min |
| 18:19 | 🚛 6E67 | Margam T.C. → Scunthorpe B.S.C.(Ent.C.) Up (S → N) | no show |
| 18:23 | 🚆 2T50 | Worcester Shrub Hill → Bristol Temple Meads Down (N → S) | active |
| 18:29 | 🚄 1V63 | Manchester Piccadilly → Bristol Temple Meads Down (N → S) | on time |
On today’s timetable, Alstone crossing is predicted to be closed for about 7 h 53 min between 06:00 and 22:00, across roughly 92 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: 11.1 min (11:11–11:23, 4 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:11–08:11 in the morning and around 12:25–13:25 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Alstone is a manually-controlled barrier crossing (MCB/MB) on the Worcestershire Parkway HL–Cheltenham Spa line (Western route · ELR BAG2). 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 697 trains through this crossing.
94.7% of observed passes were being warned about on this page when they passed, and 96.9% of the warnings we could verify came true.
Typical timing error was ±7s (9 in 10 within 38s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.