Attleborough level crossing

Manually-controlled barrier with obstacle detection level crossing on the Anglia route (ELR ETN).

right now
OPEN
for at least 2h

Next 30 min

OPEN 01:10–03:10+ 2h+
Under the hood
Fri 24 Jul · 01:10
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:10:37 · 78 avg · 0 in window
lx berths down: EN/8173→EN/[email protected] · down: EN/8195→EN/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,791 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Attleborough crossing is predicted to be closed for about 4 h 27 min between 06:00 and 22:00, across roughly 56 closures. The longest single predicted closure is 7 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.

Worst times to cross today

Closures cluster around 07:53–08:53 in the morning and around 14:08–15:08 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Attleborough is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Thetford–Spooner Row line (Anglia route · ELR ETN). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 220 trains through this crossing.

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

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

Full accuracy report →

Is this right?