Pools (No 2) level crossing

User-worked with stop lights level crossing on the Anglia route (ELR ETN).

predicted
OPEN
for 11 min

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

next: πŸš„ in 12 min Β· 1 min early

Next 30 min

OPEN 09:59–10:10 11m
CLOSED 10:10–10:11 50s
OPEN 10:11–10:32 β†’ 22m
Under the hood
Thu 22 Oct Β· 09:59
Today Tomorrow

Trains in window

09:53 πŸš„ 1K62 Cambridge β†’ Norwich Down (W β†’ E) +1 min
10:11 πŸš„ 1K67 Norwich β†’ Stansted Airport Up (E β†’ W) approaching
10:26 ❓ 0H03 Brandon Goods Loop β†’ Brandon Goods Loop Up (E β†’ W) cancelled
πŸš„Express passenger ❓Other
now 09:59:25 Β· 82 avg Β· 3 in window
live observation: 1 up Β· 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active Β· 31,698 delays Β· 1,962 cancelled Β· 9 reconnects
About this crossing

How often it closes

On today’s timetable, Pools (No 2) crossing is predicted to be closed for about 2 h 10 min between 06:00 and 22:00, across roughly 66 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 (06:20–06:20, 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 10:53–11:53 in the morning and around 12:00–13:00 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

The crossing is near Sedge Fen, Suffolk.

Pools (No 2) is a user-worked with stop lights crossing (UWCMSL) on the Ely–Thetford line (Anglia route · ELR ETN). 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 433 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 Β±21s (9 in 10 within 214s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report β†’

Is this right?