Stewartby Brickworks level crossing

CCTV-monitored manual barrier level crossing on the West Coast South route (ELR BBM).

right now
OPEN
for at least 2h

Next 30 min

OPEN 00:18–02:18+ 2h+
Under the hood
Fri 24 Jul · 00:18
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 00:18:12 · 49 avg · 0 in window
lx berths down: RT/0023→RT/[email protected] · up: RT/0024→RT/[email protected] · up: RT/0028→RT/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,038 active · 29,999 delays · 1,740 cancelled · 0 reconnects
Nearby crossings

All 154 crossings in North West and Central →

About this crossing

How often it closes

On today’s timetable, Stewartby Brickworks crossing is predicted to be closed for about 2 h 27 min between 06:00 and 22:00, across roughly 36 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 06:00–07:00 in the morning and around 16:52–17:52 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Stewartby Brickworks is a cctv-monitored manual barrier crossing (CCTV) on the Bletchley–Up line (West Coast South route · ELR BBM). 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 109 trains through this crossing.

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

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

Full accuracy report →

Is this right?