Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR HUL3).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:27 | 🚆 2K08 | Halifax → Hull Down (W → E) | +4 min |
| 09:33 | 🚆 2R72 | Bridlington → York Up (E → W) | +1 min |
| 09:39 | 🚄 1K12 | Hull → Liverpool Lime Street HL/ML Up (E → W) | +1 min |
| 09:51 | 🚆 2K11 | Hull → Halifax Up (E → W) | on time |
| 09:52 | 🚄 1K11 | Liverpool Lime Street HL/ML → Hull Down (W → E) | +6 min |
On today’s timetable, Thorpe Gates crossing is predicted to be closed for about 6 h 46 min between 06:00 and 22:00, across roughly 93 closures. The longest single predicted closure is 7 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: 3.2 min (05:39–05:43, 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 07:52–08:52 in the morning and around 12:03–13:03 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 Gates is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Micklefield–Selby line (North and East route · ELR HUL3). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 355 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.6% of the warnings we could verify came true.
Typical timing error was ±63s (9 in 10 within 267s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.