Automatic open level crossing level crossing on the East Coast route (ELR KWS).
| 01:01 | 4R40 | 🚃 | DRAXCEG → IMNGBIO | → from Heck (FLHH) | -12 min |
| 01:03 | 4S73 | 🚛 | MBROSTY → MOSEDNY | ← from Doncaster West Yard | no show |
| 01:17 | 1N35 | 🚄 | KNGX → YORK | ← from Doncaster West Yard | -9 min |
| 01:18 | 6E36 | 🚛 | MLRHY → DONCUDY | → from Heck (FLHH) | -12 min |
| 01:21 | 6V90 | 🚛 | DRAXCEG → APPLEFS | → from Heck (FLHH) | no show |
| 01:34 | 6H50 | 🚛 | IMNGBIO → DRAXCEG | ← from Doncaster West Yard | -19 min |
On today’s timetable, Thorpe crossing is predicted to be closed for about 6 h 40 min between 06:00 and 22:00, across roughly 117 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: 1.5 min (00:25–00:26, 1 train), 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:36–09:36 in the morning and around 13:04–14:04 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Thorpe is a automatic open level crossing crossing (AOCL) on the Doncaster West Yard–Heck (FLHH) line (East Coast route · ELR KWS). The approaching train itself triggers the closure at a fixed point on its approach. 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 106 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 97.3% of the warnings we could verify came true.
Typical timing error was ±46s (9 in 10 within 174s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.