Camberley level crossing

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

predicted
CLOSED
for 3 min

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

next: πŸš† now Β· on time

Next 30 min

CLOSED 09:58–10:01 3m
OPEN 10:01–10:10 9m
CLOSED 10:10–10:14 3m
OPEN 10:14–10:36 β†’ 23m
Under the hood
Thu 22 Oct Β· 09:58
Today Tomorrow

Trains in window

09:58 πŸš† 2N19 Ascot β†’ Aldershot Down (NE β†’ SW) approaching
10:01 🚧 3S83 Effingham Jn. C.H.S. β†’ Effingham Jn. C.H.S. Up (SW β†’ NE) +1 min
10:13 πŸš† 2N26 Aldershot β†’ Ascot Up (SW β†’ NE) active
πŸš†Passenger 🚧Engineering
now 09:58:55 Β· 81 avg Β· 3 in window
live observation: 1 up Β· 2 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active Β· 31,698 delays Β· 1,962 cancelled Β· 9 reconnects
Nearby crossings

All 234 crossings in Southern β†’

About this crossing

How often it closes

On today’s timetable, Camberley crossing is predicted to be closed for about 5 h between 06:00 and 22:00, across roughly 65 closures. The longest single predicted closure is 6 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: 5.9 min (09:37–09:42, 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 06:23–07:23 in the morning and around 18:35–19:35 in the evening. 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 Heathcote Road in Camberley, Surrey, next to the station.

Camberley is a CCTV-monitored manual barrier crossing (CCTV) on the Ascot–Aldershot line (Wessex route · ELR AAV). 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 504 trains through this crossing.

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

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

Full accuracy report β†’

Is this right?