Saltmarshe level crossing

Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR TJG2).

predicted
OPEN
for 21 min

Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.

next: πŸš† in 24 min Β· 1 min late

Next 30 min

OPEN 09:59–10:20 21m
CLOSED 10:20–10:24 3m
OPEN 10:24–10:37 β†’ 13m
Under the hood
Thu 22 Oct Β· 09:59
Today Tomorrow

Trains in window

09:54 πŸš„ 1J43 Bridlington β†’ Sheffield Up (NE β†’ SW) +3 min
10:23 πŸš† 2C56 Hull β†’ Doncaster Up (NE β†’ SW) +1 min
πŸš„Express passenger πŸš†Passenger
now 09:59:28 Β· 82 avg Β· 2 in window
live observation: 1 up Β· 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active Β· 31,698 delays Β· 1,962 cancelled Β· 9 reconnects
Nearby crossings

All 866 crossings in Eastern β†’

About this crossing

How often it closes

On today’s timetable, Saltmarshe crossing is predicted to be closed for about 3 h 59 min 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:42–05:46, 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.

Worst times to cross today

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.

About this crossing

The crossing is on Trandy Lane in Laxton, East Riding of Yorkshire, next to Saltmarshe station.

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.

How accurate is this forecast?

We score this page against what actually happened on the railway: over the last 7 days that covered 174 trains through this crossing.

100.0% of observed passes were being warned about on this page when they passed, and 98.7% of the warnings we could verify came true.

Typical timing error was Β±3s (9 in 10 within 123s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report β†’

Is this right?