Kirton Lane level crossing

CCTV-monitored manual barrier level crossing on the East Coast route (ELR DOW).

right now
CLOSED
for 1 min
next: 🚛 in 1 min · 19 min early

Next 30 min

CLOSED 01:14–01:16 1m
OPEN 01:16–02:29 → 73m
Under the hood
Fri 24 Jul · 01:14
Today Tomorrow

Trains in window

01:13 4R40 🚃 DRAXCEG → IMNGBIO → from Goole -16 min
01:15 6H50 🚛 IMNGBIO → DRAXCEG ← from Scunthorpe B.S.C.(Ent.C.) -19 min
01:16 6D10 🚛 PBROVGB → BNTBGBR → from Goole cancelled
🚃Empty stock 🚛Freight
now 01:14:44 · 216 avg · 3 in window
lx berths down: DR/0629→DR/[email protected] · up: DR/0628→DR/[email protected] · up: DR/0635→DR/[email protected] · up: DR/0636→DR/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,797 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Kirton Lane crossing is predicted to be closed for about 7 h 33 min between 06:00 and 22:00, across roughly 86 closures. The longest single predicted closure is 13 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 (01:10–01:13, 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 07:29–08:29 in the morning and around 13:06–14:06 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

Kirton Lane is a cctv-monitored manual barrier crossing (CCTV) on the Scunthorpe B.S.C.(Ent.C.)–Goole line (East Coast route · ELR DOW). 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 515 trains through this crossing.

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

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

Full accuracy report →

Is this right?