Nether Poppleton level crossing

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

predicted
OPEN
for 8 min

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

next: 🚆 in 11 min · on time

Next 30 min

OPEN 15:02–15:10 8m
CLOSED 15:10–15:13 3m
MAY OPEN 15:13–15:14 2m
CLOSED 15:14–15:18 3m
OPEN 15:18–15:38 → 20m
Under the hood
Mon 07 Sep · 15:02
Today Tomorrow

Trains in window

15:13 🚆 2C32 LeedsYork Up (W → E) on time
15:18 🚆 2C39 YorkLeeds Down (E → W) active
🚆Passenger
now 15:02:03 · 59 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 50,276 active · 35,154 delays · 3,473 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Nether Poppleton crossing is predicted to be closed for about 4 h 11 min between 06:00 and 22:00, across roughly 57 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.

Longest closure so far today: 3.2 min (07:23–07:26, 1 train), 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 08:16–09:16 in the morning and around 13:40–14:40 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

Nether Poppleton is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the York–Harrogate line (East Coast route · ELR HAY1). 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 210 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 ±4s (9 in 10 within 156s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?