Langford level crossing

Automatic half-barrier level crossing on the East Coast route (ELR NOB1).

predicted
OPEN
for 5 min

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

next: 🚄 in 6 min · 2 min late

Next 30 min

OPEN 13:03–13:08 5m
CLOSED 13:08–13:09 2m
OPEN 13:09–13:22 12m
CLOSED 13:22–13:23 2m
OPEN 13:23–13:31 8m
CLOSED 13:31–13:32 1m
OPEN 13:32–13:37 → 4m
Under the hood
Mon 07 Sep · 13:03
Today Tomorrow

Trains in window

13:01 🚄 1K67 LincolnCrewe Up (NE → SW) passed
13:09 🚄 1N58 CreweLincoln Down (SW → NE) +2 min
13:23 🚆 2N59 MatlockLincoln Down (SW → NE) +3 min
13:32 🚆 2A24 CleethorpesMatlock Up (NE → SW) +1 min
🚄Express passenger 🚆Passenger
now 13:03:52 · 81 avg · 4 in window
live observation: 1 up · 0 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 49,991 active · 32,739 delays · 3,335 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Langford crossing is predicted to be closed for about 2 h 46 min between 06:00 and 22:00, across roughly 75 closures. The longest single predicted closure is 3 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: 1.5 min (05:37–05:39, 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 06:13–07:13 in the morning and around 15:17–16:17 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Langford is a automatic half-barrier crossing (AHB) on the Newark North Gate–Hykeham line (East Coast route · ELR NOB1). 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 287 trains through this crossing.

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

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

Full accuracy report →

Is this right?