CCTV-monitored manual barrier level crossing on the Western route (ELR MLN1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:59 | 🚄 1C41 | London Paddington → Swindon Down (E → W) | -1 min |
| 10:03 | 🚛 4V87 | Ipswich S.S. → Stoke Gifford FHH Down (E → W) | no show |
| 10:06 | 🚄 1C08 | London Paddington → Bristol Temple Meads Down (E → W) | approaching |
| 10:15 | 🚄 1G09 | London Paddington → Gloucester Down (E → W) | on time |
| 10:16 | 🚄 1L68 | Gloucester → London Paddington Up (W → E) | on time |
| 10:19 | 🚄 1A45 | Bristol Temple Meads → London Paddington Up (W → E) | +12 min |
| 10:19 | 🚄 1N57 | Oxford → Bristol Temple Meads Down (E → W) | active |
| 10:26 | 🚄 1B09 | London Paddington → Swansea Down (E → W) | on time |
| 10:28 | 🚄 1A14 | Bristol Temple Meads → London Paddington Up (W → E) | +7 min |
| 10:32 | 🚄 1L12 | Swansea → London Paddington Up (W → E) | on time |
On today’s timetable, Causeway crossing is predicted to be closed for about 9 h 31 min between 06:00 and 22:00, across roughly 114 closures. The longest single predicted closure is 11 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: 9.4 min (08:07–08:17, 3 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 10:50–11:50 in the morning and around 12:06–13:06 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on The Causeway in Steventon, Oxfordshire.
Causeway is a CCTV-monitored manual barrier crossing (CCTV) on the Didcot Parkway–Swindon line (Western route · ELR MLN1). 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,634 trains through this crossing.
99.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 ±3s (9 in 10 within 43s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.