CCTV-monitored manual barrier level crossing on the Western route (ELR DCL).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 04:58 | 🚛 6M54 | Stoke Gifford FHH → Oxford Banbury Road Down (S → N) | no show |
| 05:04 | ❓ 0M44 | Eastleigh East Yard → Kineton MOD GBRf Down (S → N) | no show |
| 05:12 | 🚛 3Z07 | Birmingham New Street → Reading Triangle Sidings Up (N → S) | -71 min |
| 05:28 | 🚄 1D03 | Oxford → London Paddington Up (N → S) | active |
On today’s timetable, Appleford crossing is predicted to be closed for about 11 h 11 min between 06:00 and 22:00, across roughly 102 closures. The longest single predicted closure is 16 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 (04:34–04:37, 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 08:19–09:19 in the morning and around 18:11–19:11 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Appleford is a cctv-monitored manual barrier crossing (CCTV) on the Didcot T.C.–Hinksey Sdgs line (Western route · ELR DCL). 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 1,469 trains through this crossing.
99.9% of observed passes were being warned about on this page when they passed, and 98.9% of the warnings we could verify came true.
Typical timing error was ±9s (9 in 10 within 211s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.