Betchworth level crossing

CCTV-monitored manual barrier level crossing on the Sussex route (ELR RSJ).

predicted
CLOSED
for 2 min

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

next: πŸš„ now Β· 8 min late

Next 30 min

CLOSED 07:28–07:29 2m
OPEN 07:29–07:40 10m
CLOSED 07:40–07:43 3m
OPEN 07:43–08:17 β†’ 34m
Under the hood
Mon 12 Oct Β· 07:28
Today Tomorrow

Trains in window

07:28 πŸš„ 1V37 Gatwick Airport β†’ Reading Down (NE β†’ SW) +8 min
07:29 πŸš„ 1O55 Reading β†’ Gatwick Airport Up (SW β†’ NE) approaching
07:43 πŸš† 2V38 Redhill β†’ Reading Down (NE β†’ SW) active
πŸš„Express passenger πŸš†Passenger
now 07:28:02 Β· 52 avg Β· 3 in window
live observation: 1 up Β· 1 down
timetable cif full+upd 2026-10-11..2026-10-13
fetched 02:08:22
trust 48,777 active Β· 25,562 delays Β· 2,540 cancelled Β· 0 reconnects
Nearby crossings

All 234 crossings in Southern β†’

About this crossing

How often it closes

On today’s timetable, Betchworth crossing is predicted to be closed for about 4 h 37 min between 06:00 and 22:00, across roughly 62 closures. The longest single predicted closure is 8 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: 4.4 min (05:32–05:36, 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:50–10:50 in the morning and around 12:33–13:33 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

The crossing is on Station Road near Betchworth, Surrey, next to the station.

Betchworth is a CCTV-monitored manual barrier crossing (CCTV) on the Reigate–Haslemere line (Sussex route · ELR RSJ). 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 170 trains through this crossing.

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

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

Full accuracy report β†’

Is this right?