St. Andrew's Jn level crossing

Manually-controlled barrier level crossing on the Western route (ELR AMB).

right now
OPEN
for at least 2h

Next 30 min

OPEN 01:15–03:15+ 2h+
Under the hood
Fri 24 Jul · 01:15
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:15:44 · 47 avg · 0 in window
lx berths down: D0/A004→D0/[email protected] · up: D0/A005→D0/[email protected] · up: D0/A007→D0/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,797 cancelled · 0 reconnects
Nearby crossings

All 228 crossings in Wales & Western →

About this crossing

How often it closes

On today’s timetable, St. Andrew's Jn crossing is predicted to be closed for about 3 h between 06:00 and 22:00, across roughly 40 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 06:15–07:15 in the morning and around 19:45–20:45 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

St. Andrew's Jn is a manually-controlled barrier crossing (MCB/MB) on the Severn Beach–Avonmouth line (Western route · ELR AMB). 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 350 trains through this crossing.

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

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

Full accuracy report →

Is this right?