Burton Joyce level crossing

Automatic half-barrier level crossing on the East Midlands route (ELR NOB1).

predicted
OPEN
for 25 min

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

next: 🚃 in 27 min · 1 min early

Next 30 min

OPEN 04:55–05:21 25m
CLOSED 05:21–05:22 2m
OPEN 05:22–05:28 → 6m
Under the hood
Mon 07 Sep · 04:55
Today Tomorrow

Trains in window

05:22 🚃 5E16 Etches Park SdgsLincoln Down (SW → NE) -1 min
🚃Empty stock
now 04:55:57 · 62 avg · 1 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,565 delays · 2,955 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Burton Joyce crossing is predicted to be closed for about 2 h 24 min between 06:00 and 22:00, across roughly 55 closures. The longest single predicted closure is 4 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 06:35–07:35 in the morning and around 12:54–13:54 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

Burton Joyce is a automatic half-barrier crossing (AHB-X) on the Nottingham–Thurgarton line (East Midlands route · ELR NOB1). The approaching train itself triggers the closure at a fixed point on its approach. 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 446 trains through this crossing.

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

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

Full accuracy report →

Is this right?