CCTV-monitored manual barrier level crossing on the Western route (ELR BHL).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:54 | 🚄 1J74 | Plymouth → London Paddington Up (W → E) | +5 min |
| 09:55 | 🚄 1K11 | Newbury → London Paddington Up (W → E) | passed |
| 10:03 | 🚄 1C74 | London Paddington → Plymouth Down (E → W) | approaching |
| 10:15 | 🚆 2K31 | Newbury → Reading Up (W → E) | active |
| 10:15 | 🚛 6A40 | Merehead Quarry (FHH) → Hanwell Bridge Loop Up (W → E) | approaching |
| 10:19 | 🚄 1K06 | London Paddington → Newbury Down (E → W) | +23 min |
| 10:26 | 🚄 1C75 | London Paddington → Paignton Down (E → W) | +12 min |
| 10:26 | 🚄 1K13 | Newbury → London Paddington Up (W → E) | active |
On today’s timetable, Thatcham crossing is predicted to be closed for about 6 h 48 min between 06:00 and 22:00, across roughly 89 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: 14.7 min (07:23–07:38, 4 trains), measured from this crossing’s protecting signals: the signal can only show a proceed aspect with the barriers proven down, so this is the signalling system’s own record of the barriers, with standard allowances for the lowering sequence and the raise. It can differ from the forecast timeline above: this is what actually happened, not what was predicted.
Closures cluster around 08:58–09:58 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.
The crossing is on Station Road in Thatcham, Berkshire, next to the station.
Thatcham is a CCTV-monitored manual barrier crossing (CCTV) on the Midgham–Newbury line (Western route · ELR BHL). 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 805 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.6% of the warnings we could verify came true.
Typical timing error was ±11s (9 in 10 within 55s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.