Hampton Court level crossing

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

right now
OPEN
for 7 min
next: 🚃 in 10 min · running

Next 30 min

OPEN 00:16–00:22 7m
CLOSED 00:22–00:26 3m
OPEN 00:26–02:16+ 1h+
Under the hood
Fri 24 Jul · 00:16
Today Tomorrow

Trains in window

00:13 2J75 🚆 WATRLMN → HCRT ← from Surbiton +1 min
00:25 5Y72 🚃 HCRT → WDONPDS ← from Surbiton active
🚆Passenger 🚃Empty stock
now 00:16:14 · 80 avg · 2 in window
lx berths down: SU/0531→SU/[email protected] · up: SU/0529→SU/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,036 active · 29,996 delays · 1,739 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Hampton Court crossing is predicted to be closed for about 4 h 49 min between 06:00 and 22:00, across roughly 64 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: 3.2 min (00:09–00:12, 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 06:00–07:00 in the morning and around 19:26–20:26 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Hampton Court is a cctv-monitored manual barrier crossing (CCTV) on the Surbiton–Up line (Wessex route · ELR HAM). 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 233 trains through this crossing.

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

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

Full accuracy report →

Is this right?