Long Eaton Town level crossing

CCTV-monitored manual barrier level crossing on the East Midlands route (ELR TCC).

right now
OPEN
for the next 30 min

Next 30 min

OPEN 02:05–02:58 → 53m
Under the hood
Fri 24 Jul · 02:05
Today Tomorrow

Trains in window

02:02 6F46 🚧 STAPLCE → CLIFGBR → from Toton North Yard sched
🚧Engineering
now 02:05:49 · 142 avg · 1 in window
lx berths up: NE/4570→NE/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,100 active · 30,165 delays · 1,826 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Long Eaton Town crossing is predicted to be closed for about 1 h 27 min between 06:00 and 22:00, across roughly 20 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 06:38–07:38 in the morning and around 14:35–15:35 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Long Eaton Town is a cctv-monitored manual barrier crossing (CCTV) on the Loughborough–Toton North Yard line (East Midlands route · ELR TCC). 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 41 trains through this crossing.

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

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

Full accuracy report →

Is this right?