Naas level crossing

Automatic half-barrier level crossing on the Wales route (ELR SWM2).

predicted
OPEN
for the next 30 min

Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.

next: 🚄 in 13 min · running

Next 30 min

OPEN 07:12–07:53 → 42m
Under the hood
Mon 07 Sep · 07:12
Today Tomorrow

Trains in window

07:10 🚄 1V02 Birmingham New StreetCardiff Central Down (NE → SW) passed
07:25 🚄 1M00 Cardiff CentralNottingham Up (SW → NE) no reports
🚄Express passenger
now 07:12:08 · 77 avg · 2 in window
live observation: 0 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 49,149 active · 25,036 delays · 3,031 cancelled · 0 reconnects
Nearby crossings

All 235 crossings in Wales & Western →

About this crossing

How often it closes

On today’s timetable, Naas crossing is predicted to be closed for about 2 h 17 min between 06:00 and 22:00, across roughly 52 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.

Longest closure so far today: 1.5 min (04:12–04:14, 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 09:56–10:56 in the morning and around 17:24–18:24 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Naas is a automatic half-barrier crossing (AHB) on the Gloucester–Llanwern Exchange Sdgs line (Wales route · ELR SWM2). 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 200 trains through this crossing.

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

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

Full accuracy report →

Is this right?