Elsenham level crossing

Level level crossing on the Anglia route (ELR BGK).

predicted
OPEN
for 16 min

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

next: 🚆 in 16 min · on time

Next 30 min

OPEN 04:55–05:11 16m
CLOSED 05:11–05:12 50s
OPEN 05:12–05:15 3m
CLOSED 05:15–05:16 50s
OPEN 05:16–05:33 → 18m
Under the hood
Mon 07 Sep · 04:55
Today Tomorrow

Trains in window

05:12 🚆 2K51 CambridgeStansted Airport Up (NW → SE) approaching
05:16 🚆 2H01 CambridgeLondon Liverpool Street Up (NW → SE) +1 min
🚆Passenger
now 04:55:57 · 152 avg · 2 in window
live observation: 2 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,724 active · 21,566 delays · 2,955 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Elsenham crossing is predicted to be closed for about 3 h 50 min between 06:00 and 22:00, across roughly 119 closures. The longest single predicted closure is 3 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 09:57–10:57 in the morning and around 19:45–20:45 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Elsenham is a level crossing (WG) on the Bishops Stortford–Audley End 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 1,014 trains through this crossing.

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

Typical timing error was ±5s (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?