Strumpshaw level crossing

CCTV-monitored manual barrier level crossing on the Anglia route (ELR NOL).

predicted
OPEN
for 11 min

Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.

next: 🚆 in 14 min · running

Next 30 min

OPEN 16:51–17:02 11m
CLOSED 17:02–17:06 3m
MAY OPEN 17:06–17:07 2m
CLOSED 17:07–17:10 3m
OPEN 17:10–18:01 → 51m
Under the hood
Thu 08 Oct · 16:51
Today Tomorrow

Trains in window

17:05 🚆 2J84 Norwich → Lowestoft Down (NW → SE) active
17:10 🚆 2J85 Lowestoft → Norwich Up (SE → NW) approaching
🚆Passenger
now 16:51:38 · 57 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-07..2026-10-09
fetched 02:08:26
trust 33,615 active · 32,041 delays · 2,179 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Strumpshaw crossing is predicted to be closed for about 2 h 54 min between 06:00 and 22:00, across roughly 37 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.

Longest closure so far today: 6.8 min (08:00–08:07, 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.

Worst times to cross today

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

About this crossing

Strumpshaw is a cctv-monitored manual barrier crossing (CCTV) on the Norwich C.Pt. T.&R.S.M.D–Reedham (Norfolk) line (Anglia route · ELR NOL). A signaller monitors the crossing, confirms it is clear, and lowers the barriers ahead of each train. 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 367 trains through this crossing.

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

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

Full accuracy report →

Is this right?