Rolleston Station level crossing

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

right now
OPEN
for the next 30 min

Next 30 min

OPEN 01:11–02:11 → 59m
Under the hood
Fri 24 Jul · 01:11
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:11:50 · 82 avg · 0 in window
lx berths down: NM/4073→NM/[email protected] · up: NM/4074→NM/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,795 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

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

Rolleston Station is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Nottingham–Rolleston line (East Midlands route · ELR NOB1). 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 247 trains through this crossing.

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

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

Full accuracy report →

Is this right?