CCTV-monitored manual barrier level crossing on the Anglia route (ELR HEB).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 12:54 | 🚆 2O28 | London Liverpool Street → Hertford East Down (E → W) | +2 min |
| 13:01 | 🚆 2Z03 | Hertford East → London Liverpool Street Up (W → E) | passed |
| 13:10 | 🚆 2O31 | Hertford East → London Liverpool Street Up (W → E) | active |
| 13:23 | 🚆 2O30 | London Liverpool Street → Hertford East Down (E → W) | approaching |
On today’s timetable, Ware crossing is predicted to be closed for about 4 h 28 min between 06:00 and 22:00, across roughly 75 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 (07:19–07:25, 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 06:56–07:56 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.
Ware is a cctv-monitored manual barrier crossing (CCTV) on the Broxbourne–Hertford East line (Anglia route · ELR HEB). 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 544 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 ±23s (9 in 10 within 128s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.