Brook level crossing

Manually-controlled barrier with obstacle detection level crossing on the Wessex route (ELR RSJ).

predicted
OPEN
for 6 min

Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.

next: 🚄 in 8 min · 1 min early

Next 30 min

OPEN 11:09–11:14 6m
CLOSED 11:14–11:17 2m
OPEN 11:17–11:31 15m
CLOSED 11:31–11:34 3m
OPEN 11:34–11:48 → 14m
Under the hood
Mon 07 Sep · 11:09
Today Tomorrow

Trains in window

11:06 🚄 1V44 Gatwick AirportReading Down (E → W) passed
11:16 🚄 1O65 ReadingGatwick Airport Up (W → E) approaching
11:34 🚄 1V45 Gatwick AirportReading Down (E → W) +2 min
🚄Express passenger
now 11:09:10 · 74 avg · 3 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 49,728 active · 30,422 delays · 3,239 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Brook crossing is predicted to be closed for about 3 h 52 min between 06:00 and 22:00, across roughly 64 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.

Longest closure so far today: 3.4 min (07:59–08:02, 2 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.

Worst times to cross today

Closures cluster around 09:33–10:33 in the morning and around 20:33–21:33 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Brook is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Reigate–Haslemere line (Wessex route · ELR RSJ). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 435 trains through this crossing.

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

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

Full accuracy report →

Is this right?