Automatic half-barrier level crossing on the Sussex route (ELR KJE3).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 11:06 | 🚄 1F14 | London Victoria (C) → Eastbourne Down (NW → SE) | +29 min |
| 11:10 | 🚄 1F16 | London Victoria (C) → Ore Down (NW → SE) | approaching |
| 11:12 | 🚆 2U23 | Eastbourne → Brighton Up (SE → NW) | approaching |
| 11:16 | 🚄 1F25 | Ore → London Victoria (C) Up (SE → NW) | on time |
| 11:26 | 🚆 2U24 | Brighton → Eastbourne Down (NW → SE) | -1 min |
| 11:40 | 🚄 1U23 | Ore → Brighton Up (SE → NW) | +1 min |
On today’s timetable, Wilmington crossing is predicted to be closed for about 4 h 40 min between 06:00 and 22:00, across roughly 102 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: 3.5 min (05:34–05:38, 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 07:45–08:45 in the morning and around 15:54–16:54 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Wilmington is a automatic half-barrier crossing (AHB) on the Lewes–Willingdon Jn line (Sussex route · ELR KJE3). 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 882 trains through this crossing.
99.8% 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 ±61s (9 in 10 within 404s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.