Sutton Forest level crossing

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

predicted
OPEN
for at least 2h

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

Next 30 min

OPEN 02:11–04:11+ 2h+
Under the hood
Mon 07 Sep · 02:11
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:11:03 · 44 avg · 0 in window
live observation: 1 up · 2 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,282 active · 21,043 delays · 2,870 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Sutton Forest crossing is predicted to be closed for about 1 h 20 min between 06:00 and 22:00, across roughly 40 closures. The longest single predicted closure is 1 minute. 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:50–07:50 in the morning and around 16:50–17:50 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Sutton Forest is a automatic half-barrier crossing (AHB) on the Sutton Parkway–Mansfield Woodhouse line (East Midlands route · ELR PBS2). 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 288 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 ±8s (9 in 10 within 386s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?