Wood Lane level crossing

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

right now
OPEN
for 9 min
next: 🚆 in 12 min · 3 min late

Next 30 min

OPEN 00:17–00:26 9m
CLOSED 00:26–00:29 3m
OPEN 00:29–02:17+ 1h+
Under the hood
Fri 24 Jul · 00:17
Today Tomorrow

Trains in window

00:29 2S79 🚆 WATRLMN → HOUNSLW ← from Barnes +3 min
🚆Passenger
now 00:17:09 · 150 avg · 1 in window
lx berths down: B1/2359→B1/[email protected] · up: B1/2358→B1/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,036 active · 29,997 delays · 1,739 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Wood Lane crossing is predicted to be closed for about 6 h 25 min between 06:00 and 22:00, across roughly 90 closures. The longest single predicted closure is 7 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:55–08:55 in the morning and around 15:36–16:36 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Wood Lane is a cctv-monitored manual barrier crossing (CCTV) on the Barnes–Hounslow 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 689 trains through this crossing.

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

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

Full accuracy report →

Is this right?