Park Road level crossing

CCTV-monitored manual barrier level crossing on the East Midlands route (ELR SPD1).

right now
OPEN
for 9 min
next: 🚛 in 12 min · 11 min early

Next 30 min

OPEN 01:12–01:21 9m
CLOSED 01:21–01:24 3m
OPEN 01:24–01:27 3m
CLOSED 01:27–01:32 4m
OPEN 01:32–01:49 → 17m
Under the hood
Fri 24 Jul · 01:12
Today Tomorrow

Trains in window

01:04 6O18 🚛 HESSVLH → DOLMORS → from Sleaford no show
01:24 4L20 🚛 DONCIGB → FLXSSGB → from Sleaford -11 min
01:26 6V85 🚛 TINSLYY → ACTONTC → from Sleaford no show
01:30 4E19 🚛 THMSLGB → DONCIGB ← from Peterborough North Yd GBRf +17 min
01:31 4E52 🚛 WLSDEUT → HRTLPDF ← from Peterborough North Yd GBRf +6 min
🚛Freight
now 01:12:19 · 117 avg · 5 in window
lx berths down: L2/7061→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,086 active · 30,124 delays · 1,796 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Park Road crossing is predicted to be closed for about 2 h 13 min between 06:00 and 22:00, across roughly 23 closures. The longest single predicted closure is 7 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 (00:20–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:59–07:59 in the morning and around 19:07–20:07 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Park Road is a cctv-monitored manual barrier crossing (CCTV) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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 1 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 ±150s (9 in 10 within 150s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?