CCTV-monitored manual barrier level crossing on the North West route (ELR SJO2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:01 | 🚆 2U05 | Ormskirk → Hunt's Cross Up (NE → SW) | -1 min |
| 07:16 | 🚆 2O04 | Hunt's Cross → Ormskirk Down (SW → NE) | approaching |
| 07:18 | 🚆 2U06 | Ormskirk → Hunt's Cross Up (NE → SW) | approaching |
| 07:32 | 🚆 2O05 | Hunt's Cross → Ormskirk Down (SW → NE) | on time |
| 07:32 | 🚆 2U07 | Ormskirk → Hunt's Cross Up (NE → SW) | active |
On today’s timetable, Maghull crossing is predicted to be closed for about 5 h 52 min between 06:00 and 22:00, across roughly 60 closures. The longest single predicted closure is 5 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: 5.6 min (06:28–06:33, 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 07:29–08:29 in the morning and around 12:00–13:00 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Maghull is a cctv-monitored manual barrier crossing (CCTV) on the Kirkdale C.S.–Ormskirk line (North West route · ELR SJO2). 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 850 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 ±4s (9 in 10 within 29s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.