Burgess Drove level crossing

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

right now
OPEN
for 12s
next: 🚄 now · 6 min late

Next 30 min

OPEN 01:15–01:15 12s
CLOSED 01:15–01:16 35s
OPEN 01:16–01:46 → 30m
Under the hood
Fri 24 Jul · 01:15
Today Tomorrow

Trains in window

01:16 1C74 🚄 KNGX → CAMBDGE → from Ely +6 min
01:30 3S20 🚧 BROXGBF → BROXGBF → from Ely no show
🚄Express passenger 🚧Engineering
now 01:15:38 · 408 avg · 2 in window
lx berths down: CA/0235→CA/[email protected] · up: CA/0248→CA/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,797 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Burgess Drove crossing is predicted to be closed for about 6 h 13 min between 06:00 and 22:00, across roughly 174 closures. The longest single predicted closure is 5 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:02, 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 08:30–09:30 in the morning and around 17:14–18:14 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Burgess Drove is a user-worked with stop lights crossing (UWCMSL) on the Chesterton Junction FHH–Ely line (Anglia route · ELR BGK). 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 8 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 ±231s (9 in 10 within 452s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?