CCTV-monitored manual barrier level crossing on the Sussex route (ELR TBH1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:09 | 🚄 9J14 | Horsham → Peterborough Up (W → E) | +2 min |
| 07:25 | 🚄 1B06 | London Victoria (C) → Bognor Regis Down (E → W) | approaching |
| 07:29 | 🚄 1B09 | Bognor Regis → London Victoria (C) Up (W → E) | -1 min |
| 07:32 | 🚄 9J03 | Peterborough → Horsham Down (E → W) | on time |
| 07:37 | 🚄 9J16 | Horsham → Peterborough Up (W → E) | active |
On today’s timetable, Crawley High Street crossing is predicted to be closed for about 5 h 56 min between 06:00 and 22:00, across roughly 101 closures. The longest single predicted closure is 4 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: 4.1 min (06:01–06:05, 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 08:41–09:41 in the morning and around 20:04–21:04 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Crawley High Street is a cctv-monitored manual barrier crossing (CCTV) on the Three Bridges–Horsham line (Sussex route · ELR TBH1). 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 951 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.4% of the warnings we could verify came true.
Typical timing error was ±72s (9 in 10 within 108s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.