Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR BWC).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 10:59 | 🚆 2T21 | Newcastle → Ashington Down (S → N) | -2 min |
| 11:08 | 🚆 2T22 | Ashington → Newcastle Up (N → S) | passed |
| 11:19 | 🚃 6N86 | Tyne Coal Terminal GBRf → Lynemouth Power Stn Down (S → N) | +1 min |
| 11:29 | 🚆 2T23 | Newcastle → Ashington Down (S → N) | approaching |
| 11:40 | 🚆 2T24 | Ashington → Newcastle Up (N → S) | active |
On today’s timetable, North Seaton crossing is predicted to be closed for about 5 h 18 min between 06:00 and 22:00, across roughly 69 closures. The longest single predicted closure is 8 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:45–05:48, 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 10:19–11:19 in the morning and around 12:56–13:56 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
North Seaton is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Northumberland Park (NE)–Lynemouth Power Stn (GBRF) line (North and East route · ELR BWC). 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 470 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 100.0% of the warnings we could verify came true.
Typical timing error was ±2s (9 in 10 within 219s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.