Bedhampton level crossing

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

right now
CLOSED
for 20s
next: 🚃 now · 7 min late

Next 30 min

CLOSED 00:14–00:14 20s
OPEN 00:14–00:36 22m
CLOSED 00:36–00:39 3m
OPEN 00:39–00:56 → 17m
Under the hood
Fri 24 Jul · 00:14
Today Tomorrow

Trains in window

00:14 5S71 🚃 PSEA → LTLHMPT → from Fratton +7 min
00:39 2P75 🚆 WATRLMN → FRATTON ← from Havant on time
🚆Passenger 🚃Empty stock
now 00:14:21 · 292 avg · 2 in window
lx berths down: HT/0025→HT/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,034 active · 29,995 delays · 1,738 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Bedhampton crossing is predicted to be closed for about 11 h 41 min between 06:00 and 22:00, across roughly 85 closures. The longest single predicted closure is 22 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:39–08:39 in the morning and around 16:54–17:54 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Bedhampton is a cctv-monitored manual barrier crossing (CCTV) on the Havant–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 881 trains through this crossing.

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

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

Full accuracy report →

Is this right?