Itford level crossing

Level level crossing on the Sussex route (ELR STS).

right now
OPEN
for at least 2h

Next 30 min

OPEN 02:04–04:04+ 2h+
Under the hood
Fri 24 Jul · 02:04
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:04:26 · 253 avg · 0 in window
lx berths down: X7/0013→X7/[email protected] · down: X7/0017→X7/[email protected] · down: X7/1573→X7/[email protected] · up: X7/0020→X7/[email protected] · up: X7/E040→X7/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,100 active · 30,165 delays · 1,822 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Itford crossing is predicted to be closed for about 5 h 25 min between 06:00 and 22:00, across roughly 175 closures. The longest single predicted closure is 2 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 (00:01–00:01, 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.

Worst times to cross today

Closures cluster around 09:51–10:51 in the morning and around 17:46–18:46 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

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.

How accurate is this forecast?

We score this page against what actually happened on the railway — over the last 7 days that covered 745 trains through this crossing.

100.0% of observed passes were being warned about on this page when they passed, and 99.6% of the warnings we could verify came true.

Typical timing error was ±42s (9 in 10 within 146s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?