Barnes (Hounslow) level crossing

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

right now
CLOSED
for 8 min
next: 🚆 now · 3 min late

Next 30 min

CLOSED 00:15–00:23 8m
OPEN 00:23–02:15+ 1h+
Under the hood
Fri 24 Jul · 00:15
Today Tomorrow

Trains in window

00:06 2S78 🚆 WEYBDGB → WATRLMN → from Twickenham -1 min
00:16 2S79 🚆 WATRLMN → HOUNSLW ← from Clapham Junction (C) approaching
00:18 2C80 🚆 RDNG4AB → WATRLMN → from Twickenham -1 min
00:22 2U79 🚆 WATRLMN → STAINES ← from Clapham Junction (C) +2 min
00:23 2O77 🚆 WATRLMN → STRWBYH ← from Clapham Junction (C) on time
🚆Passenger
now 00:15:26 · 431 avg · 5 in window
lx berths up: BS/0550→BS/[email protected] · down: BS/0551→BS/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,035 active · 29,995 delays · 1,737 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Barnes (Hounslow) crossing is predicted to be closed for about 12 h 52 min between 06:00 and 22:00, across roughly 83 closures. The longest single predicted closure is 28 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:03–00:06, 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:54–07:54 in the morning and around 17:42–18:42 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Barnes (Hounslow) is a cctv-monitored manual barrier crossing (CCTV) on the Clapham Junction (C)–Twickenham line (Wessex route · ELR HOU). 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 979 trains through this crossing.

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

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

Full accuracy report →

Is this right?