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.
| 09:51 | 🚃 5Z07 | Horsham → Streatham Hill Shed Up (SW → NE) | no show |
| 09:54 | 🚄 9J11 | Peterborough → Horsham Down (NE → SW) | passed |
| 09:55 | 🚄 1B19 | Bognor Regis → London Victoria (C) Up (SW → NE) | no show |
| 09:58 | 🚄 9J24 | Horsham → Peterborough Up (SW → NE) | passed |
| 10:01 | 🚄 9J26 | Horsham → Peterborough Up (SW → NE) | active |
| 10:02 | 🚄 9J13 | Peterborough → Horsham Down (NE → SW) | approaching |
| 10:14 | 🚄 1C16 | London Victoria (C) → Portsmouth Harbour Down (NE → SW) | +21 min |
| 10:21 | 🚄 1B21 | Bognor Regis → London Victoria (C) Up (SW → NE) | approaching |
| 10:27 | 🚄 1C18 | London Victoria (C) → Portsmouth Harbour Down (NE → SW) | +4 min |
| 10:29 | 🚄 9J28 | Horsham → Peterborough Up (SW → NE) | active |
On today’s timetable, Littlehaven crossing is predicted to be closed for about 7 h 29 min between 06:00 and 22:00, across roughly 91 closures. The longest single predicted closure is 8 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: 7.3 min (06:52–06:59, 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 07:37–08:37 in the morning and around 20:44–21:44 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Rusper Road in Littlehaven, West Sussex, next to the station.
Littlehaven 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 1,007 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.5% of the warnings we could verify came true.