Level level crossing on the Sussex route (ELR STS).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 04:58 | 🚃 5C02 | Brighton → Seaford Down (N → S) | approaching |
| 05:02 | 🚛 6O12 | Hanwell Bridge Loop → Newhaven Day Aggs Down (N → S) | -25 min |
| 05:05 | 🚆 2C01 | Seaford → Brighton Up (S → N) | approaching |
| 05:10 | 🚛 6O90 | Acton T.C. → Newhaven Marine Ag Tml DBC Down (N → S) | -20 min |
| 05:12 | 🚄 1F01 | Eastbourne → London Victoria (C) Up (S → N) | +1 min |
| 05:14 | 🚄 1U02 | Brighton → Ore Down (N → S) | active |
| 05:19 | 🚃 5C04 | Brighton → Seaford Down (N → S) | active |
On today’s timetable, Itford crossing is predicted to be closed for about 5 h 44 min between 06:00 and 22:00, across roughly 183 closures. The longest single predicted closure is 3 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: 0.6 min (23:59–00:00, 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 08:37–09:37 in the morning and around 14:28–15:28 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Itford is a level crossing (UWCBMSL) on the Lewes–Newhaven Marine Ag Tml DBC line (Sussex route · ELR STS). 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,430 trains through this crossing.
99.7% of observed passes were being warned about on this page when they passed, and 99.9% of the warnings we could verify came true.
Typical timing error was ±107s (9 in 10 within 336s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.