CCTV-monitored manual barrier level crossing on the East Coast route (ELR ECM5).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 04:53 | 🚄 1Y02 | Newcastle → London Kings Cross Up (NW → SE) | passed |
| 04:58 | 🚄 9M05 | Newcastle → Liverpool Lime Street HL/ML Up (NW → SE) | approaching |
| 05:22 | 🚃 3E03 | Heaton T&R.S.M.D. → Middlesbrough Up (NW → SE) | -5 min |
| 05:23 | 🚛 4S99 | Tees Dock BSC Export Berth → Grangemouth TDG Down (SE → NW) | -26 min |
On today’s timetable, Hett Mill crossing is predicted to be closed for about 9 h 25 min between 06:00 and 22:00, across roughly 126 closures. The longest single predicted closure is 11 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: 8.8 min (00:24–00:33, 3 trains), 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:33–07:33 in the morning and around 16:17–17:17 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Hett Mill is a cctv-monitored manual barrier crossing (CCTV) on the Darlington–Tyne S.S. line (East Coast route · ELR ECM5). A signaller monitors the crossing, confirms it is clear, and lowers the barriers ahead of each train. 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 1,375 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 ±1s (9 in 10 within 181s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.