Quadring level crossing

Automatic half-barrier level crossing on the East Midlands route (ELR SPD1).

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

Next 30 min

OPEN 01:09–01:15 6m
CLOSED 01:15–01:17 2m
OPEN 01:17–01:35 18m
CLOSED 01:35–01:38 3m
OPEN 01:38–01:44 → 7m
Under the hood
Fri 24 Jul · 01:09
Today Tomorrow

Trains in window

01:17 4L20 🚛 DONCIGB → FLXSSGB → from Sleaford -11 min
01:19 6V85 🚛 TINSLYY → ACTONTC → from Sleaford no show
01:36 4E19 🚛 THMSLGB → DONCIGB ← from Peterborough North Yd GBRf +16 min
01:37 4E52 🚛 WLSDEUT → HRTLPDF ← from Peterborough North Yd GBRf +6 min
🚛Freight
now 01:09:43 · 117 avg · 4 in window
lx berths down: L2/7061→L2/[email protected] · down: L2/LSDS→L2/[email protected] · up: L2/LEUS→L2/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,084 active · 30,121 delays · 1,790 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Quadring crossing is predicted to be closed for about 1 h 19 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.

Longest closure so far today: 1.5 min (00:22–00:23, 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:53–07:53 in the morning and around 16:59–17:59 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Quadring is a automatic half-barrier crossing (AHB-X) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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 5 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 ±106s (9 in 10 within 279s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?