Leasingham Moor (uwc-Msl) level crossing

User-worked with stop lights level crossing on the East Midlands route (ELR SPD2).

right now
OPEN
for 13 min
next: 🚛 in 13 min · 8 min early

Next 30 min

OPEN 01:17–01:30 13m
CLOSED 01:30–01:31 35s
OPEN 01:31–01:39 8m
CLOSED 01:39–01:40 35s
OPEN 01:40–01:48 → 8m
Under the hood
Fri 24 Jul · 01:17
Today Tomorrow

Trains in window

01:31 4L88 🚛 LEEDFLT → THMSFLI → from Lincoln -8 min
01:40 4L39 🚛 NORMGBF → TLBYTCG → from Lincoln -8 min
🚛Freight
now 01:17:41 · 118 avg · 2 in window
lx berths down: L2/7099→L2/[email protected] · down: L2/7105→L2/[email protected] · up: L2/7100→L2/[email protected] · up: L2/7102→L2/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,796 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Leasingham Moor (uwc-Msl) crossing is predicted to be closed for about 38 min between 06:00 and 22:00, across roughly 32 closures. The longest single predicted closure is 2 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.

Worst times to cross today

Closures cluster around 07:26–08:26 in the morning and around 17:17–18:17 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Leasingham Moor (uwc-Msl) is a user-worked with stop lights crossing (UWCMSL) on the Peterborough North Yd GBRf–Lincoln line (East Midlands route · ELR SPD2). 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 194 trains through this crossing.

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

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

Full accuracy report →

Is this right?