Manually-controlled barrier with obstacle detection level crossing on the North and East route (ELR LEN3).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 10:02 | 🚄 1J57 | Middlesbrough → Carlisle Down (SW → NE) | approaching |
| 10:03 | 🚄 1J68 | Carlisle → Middlesbrough Up (NE → SW) | approaching |
| 10:20 | 🚆 2W11 | Nunthorpe → Newcastle Down (SW → NE) | on time |
On today’s timetable, Greatham crossing is predicted to be closed for about 4 h 35 min between 06:00 and 22:00, across roughly 65 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: 6.8 min (08:58–09:05, 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 08:22–09:22 in the morning and around 17:33–18:33 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Marsh House Lane in Greatham, County Durham.
Greatham is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Down–Hartlepool PD Ports FL line (North and East route · ELR LEN3). 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 532 trains through this crossing.
99.8% of observed passes were being warned about on this page when they passed, and 97.9% of the warnings we could verify came true.
Typical timing error was ±5s (9 in 10 within 16s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.