CCTV-monitored manual barrier level crossing on the East Coast route (ELR ECM7).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:22 | 🚄 1V50 | Edinburgh → Plymouth Up (N → S) | -2 min |
| 07:24 | 🚄 9S07 | Newcastle → Edinburgh Down (S → N) | on time |
| 07:46 | 🚄 1S29 | Leeds → Edinburgh Down (S → N) | approaching |
| 07:47 | 🚄 1E03 | Edinburgh → London Kings Cross Up (N → S) | +1 min |
| 07:58 | 🚆 2A22 | Newcastle → Morpeth Down (S → N) | active |
On today’s timetable, Dam Dykes crossing is predicted to be closed for about 9 h 2 min between 06:00 and 22:00, across roughly 101 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: 6.2 min (07:11–07:17, 2 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 09:15–10:15 in the morning and around 16:47–17:47 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Dam Dykes is a cctv-monitored manual barrier crossing (CCTV) on the Northumberland Park (NE)–Morpeth line (East Coast route · ELR ECM7). 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 823 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 ±2s (9 in 10 within 24s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.