Warblington level crossing

CCTV-monitored manual barrier level crossing on the Wessex route (ELR TBH2).

predicted
OPEN
for at least 2h

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

Next 30 min

OPEN 02:11–04:11+ 2h+
Under the hood
Mon 07 Sep · 02:11
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:11:33 · 128 avg · 0 in window
live observation: 1 up · 2 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,282 active · 21,043 delays · 2,870 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Warblington crossing is predicted to be closed for about 7 h 36 min between 06:00 and 22:00, across roughly 100 closures. The longest single predicted closure is 10 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:18–08:18 in the morning and around 14:10–15:10 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Warblington is a cctv-monitored manual barrier crossing (CCTV) on the Chichester–Havant line (Wessex route · ELR TBH2). 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 985 trains through this crossing.

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

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

Full accuracy report →

Is this right?