Automatic half-barrier level crossing on the Sussex route (ELR BLI1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 11:03 | 🚄 1H14 | London Victoria (C) → Littlehampton Down (E → W) | no show |
| 11:06 | 🚄 1N19 | Southampton Central → Brighton Up (W → E) | passed |
| 11:09 | 🚄 1S22 | Brighton → Portsmouth & Southsea Down (E → W) | on time |
| 11:10 | 🚆 2Y25 | Chichester → Brighton Up (W → E) | approaching |
| 11:16 | 🚄 1N24 | Brighton → Southampton Central Down (E → W) | cancelled |
| 11:16 | 🚄 1H27 | Littlehampton → London Victoria (C) Up (W → E) | standing 37 min |
| 11:31 | 🚄 1N21 | Southampton Central → Brighton Up (W → E) | active |
| 11:36 | 🚄 1S27 | Portsmouth & Southsea → Brighton Up (W → E) | active |
| 11:40 | 🚃 5N80 | Littlehampton → Lovers Walk T&R.S.M.D Up (W → E) | active |
On today’s timetable, Toddington crossing is predicted to be closed for about 6 h 51 min between 06:00 and 22:00, across roughly 143 closures. The longest single predicted closure is 5 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: 1.5 min (05:12–05:13, 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 07:37–08:37 in the morning and around 13:30–14:30 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Toddington is a automatic half-barrier crossing (AHB) on the Arundel–Littlehampton line (Sussex route · ELR BLI1). The approaching train itself triggers the closure at a fixed point on its approach. 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 642 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.8% of the warnings we could verify came true.
Typical timing error was ±17s (9 in 10 within 150s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.