Thurgarton level crossing

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

right now
OPEN
for the next 30 min

Next 30 min

OPEN 01:10–02:08 → 58m
Under the hood
Fri 24 Jul · 01:10
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:10:55 · 82 avg · 0 in window
lx berths down: NM/4065→NM/[email protected] · up: NM/4062→NM/[email protected] · up: NM/4072→NM/[email protected] · up: NM/U462→NM/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,793 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Thurgarton crossing is predicted to be closed for about 2 h 23 min between 06:00 and 22:00, across roughly 60 closures. The longest single predicted closure is 3 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:57–08:57 in the morning and around 12:49–13:49 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

Thurgarton is a automatic half-barrier crossing (AHB) on the Nottingham–Bleasby line (East Midlands route · ELR NOB1). 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 434 trains through this crossing.

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

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

Full accuracy report →

Is this right?