Church Lane level crossing

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

predicted
OPEN
for 17 min

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

next: 🚆 in 20 min · 2 min late

Next 30 min

OPEN 07:13–07:30 17m
CLOSED 07:30–07:33 3m
OPEN 07:33–07:48 → 15m
Under the hood
Mon 07 Sep · 07:13
Today Tomorrow

Trains in window

07:11 🚆 2K01 LincolnPeterborough Up (NW → SE) +17 min
07:31 🚛 4L03 Doncaster Iport GBRFFelixstowe South GBRF Up (NW → SE) no show
07:33 🚆 2K90 PeterboroughDoncaster Down (SE → NW) approaching
🚆Passenger 🚛Freight
now 07:13:25 · 79 avg · 3 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 49,152 active · 25,065 delays · 3,032 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Church Lane crossing is predicted to be closed for about 2 h 40 min between 06:00 and 22:00, across roughly 36 closures. The longest single predicted closure is 8 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 (06:38–06:41, 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 09:25–10:25 in the morning and around 14:32–15:32 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Church Lane is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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 376 trains through this crossing.

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

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

Full accuracy report →

Is this right?