Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR DSN1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:00 | 🚆 2D08 | Darlington → Saltburn Down (W → E) | -1 min |
| 07:26 | 🚆 2D10 | Bishop Auckland → Saltburn Down (W → E) | -1 min |
| 07:34 | 🚧 3J78 | Nunthorpe → Carlisle Yard Colas Rail Up (E → W) | -1 min |
| 07:41 | 🚆 2D03 | Saltburn → Darlington Up (E → W) | on time |
On today’s timetable, Urlay Nook crossing is predicted to be closed for about 4 h 34 min between 06:00 and 22:00, across roughly 52 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 (00:01–00:04, 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 06:02–07:02 in the morning and around 15:17–16:17 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Urlay Nook is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Northallerton–Tees N.Y. line (North and East route · ELR DSN1). 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 525 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.5% of the warnings we could verify came true.
Typical timing error was ±1s (9 in 10 within 6s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.