Aslockton level crossing

Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR NOG1).

predicted
OPEN
for 6 min

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

next: 🚆 in 9 min · on time

Next 30 min

OPEN 07:51–07:57 6m
CLOSED 07:57–08:00 3m
OPEN 08:00–08:33 → 33m
Under the hood
Mon 12 Oct · 07:51
Today Tomorrow

Trains in window

07:50 🚄 1L03 Nottingham → Norwich Up (W → E) passed
08:00 🚆 2S07 Nottingham → Skegness Up (W → E) on time
🚄Express passenger 🚆Passenger
now 07:51:33 · 64 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-11..2026-10-13
fetched 02:08:22
trust 48,886 active · 26,175 delays · 2,578 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Aslockton crossing is predicted to be closed for about 3 h 32 min between 06:00 and 22:00, across roughly 51 closures. The longest single predicted closure is 6 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: 4.5 min (06:15–06:19, 2 trains), 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:05–11:05 in the morning and around 17:02–18:02 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

The crossing is on Main Street in Aslockton, Nottinghamshire, next to the station.

Aslockton is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Grantham–Bingham line (East Midlands route · ELR NOG1). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 463 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 ±10s (9 in 10 within 47s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?