Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR TJG2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:25 | 🚆 2C54 | Hull → Doncaster Up (NE → SW) | approaching |
| 09:38 | 🚆 2C55 | Doncaster → Hull Down (SW → NE) | on time |
| 09:47 | 🚄 1W41 | Sheffield → Scarborough Down (SW → NE) | -2 min |
| 09:52 | 🚄 1J43 | Bridlington → Sheffield Up (NE → SW) | +1 min |
On today’s timetable, Saltmarshe crossing is predicted to be closed for about 4 h between 06:00 and 22:00, across roughly 52 closures. The longest single predicted closure is 6 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:40–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:08–08:08 in the morning and around 19:09–20:09 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Saltmarshe is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Goole–Hull Dairycoates Tlcn GBRf line (North and East route · ELR TJG2). 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 238 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.8% of the warnings we could verify came true.
Typical timing error was ±2s (9 in 10 within 37s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.