CCTV-monitored manual barrier level crossing on the Wessex route (ELR WPH2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 17:48 | 🚄 1C55 | Portsmouth & Southsea → Horsham Up (W → E) | passed |
| 17:52 | 🚄 1P51 | London Waterloo → Portsmouth Harbour Down (E → W) | +3 min |
| 17:55 | 🚄 1P62 | Portsmouth Harbour → London Waterloo Up (W → E) | approaching |
| 17:57 | 🚄 1C44 | London Victoria (C) → Portsmouth Harbour Down (E → W) | -1 min |
| 18:09 | 🚄 1N48 | Brighton → Southampton Central Down (E → W) | +24 min |
| 18:11 | 🚄 1S55 | Portsmouth & Southsea → Brighton Up (W → E) | cancelled |
| 18:13 | 🚄 1N49 | Southampton Central → Brighton Up (W → E) | +11 min |
| 18:14 | 🚄 1N50 | Brighton → Southampton Central Down (E → W) | active |
| 18:18 | 🚄 1P53 | London Waterloo → Portsmouth Harbour Down (E → W) | -1 min |
| 18:19 | 🚄 1C57 | Portsmouth Harbour → Horsham Up (W → E) | active |
| 18:24 | 🚆 2P66 | Portsmouth & Southsea → London Waterloo Up (W → E) | active |
On today’s timetable, Havant crossing is predicted to be closed for about 12 h 27 min between 06:00 and 22:00, across roughly 116 closures. The longest single predicted closure is 18 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: 13.2 min (13:34–13:48, 4 trains), 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.
Closures cluster around 07:36–08:36 in the morning and around 15:22–16:22 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Havant is a cctv-monitored manual barrier crossing (CCTV) on the Chichester–Portsmouth & Southsea 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 1,101 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.0% of the warnings we could verify came true.
Typical timing error was ±5s (9 in 10 within 53s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.