Doddington Road level crossing

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

right now
OPEN
for the next 30 min

Next 30 min

OPEN 02:04–03:12 → 68m
Under the hood
Fri 24 Jul · 02:04
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:04:55 · 98 avg · 0 in window
lx berths down: LN/7945→LN/[email protected] · up: LN/7946→LN/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,100 active · 30,165 delays · 1,822 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Doddington Road crossing is predicted to be closed for about 5 h 6 min between 06:00 and 22:00, across roughly 62 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.

Worst times to cross today

Closures cluster around 07:45–08:45 in the morning and around 13:34–14:34 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Doddington Road is a cctv-monitored manual barrier crossing (CCTV) on the Newark North Gate–Worksop line (East Midlands route · ELR NOB1). 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 560 trains through this crossing.

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

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

Full accuracy report →

Is this right?