Havant level crossing

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

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

02:13 🚧 8Y84 Totton YardTotton Yard Up (W → E) no show
🚧Engineering
now 02:11:25 · 202 avg · 1 in window
live observation: 1 up · 1 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, Havant crossing is predicted to be closed for about 11 h 30 min between 06:00 and 22:00, across roughly 111 closures. The longest single predicted closure is 13 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:40–07:40 in the morning and around 15:18–16:18 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Havant is a cctv-monitored manual barrier crossing (CCTV) on the Chichester–Fratton line (Wessex route · ELR WPH2). 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 987 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 ±4s (9 in 10 within 118s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?