Billingshurst level crossing

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

predicted
CLOSED
for 1 min

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

next: 🚄 in 1 min · 6 min late

Next 30 min

CLOSED 17:43–17:44 1m
OPEN 17:44–17:48 4m
CLOSED 17:48–17:51 3m
OPEN 17:51–18:00 9m
CLOSED 18:00–18:06 6m
OPEN 18:06–18:13 → 7m
Under the hood
Thu 08 Oct · 17:43
Today Tomorrow

Trains in window

17:36 🚄 1C51 Portsmouth Harbour → Horsham Up (W → E) -1 min
17:44 🚄 1C46 London Victoria (C) → Portsmouth Harbour Down (E → W) +6 min
17:47 🚃 5Z70 Selhurst T&R.S.M.D → Littlehampton Down (E → W) no show
17:51 🚄 1B46 Horsham → Bognor Regis Down (E → W) +6 min
18:03 🚄 1B53 Bognor Regis → London Victoria (C) Up (W → E) +1 min
18:06 🚄 1C53 Portsmouth Harbour → Horsham Up (W → E) -1 min
🚄Express passenger 🚃Empty stock
now 17:43:17 · 133 avg · 6 in window
timetable cif full+upd 2026-10-07..2026-10-09
fetched 02:08:26
trust 33,676 active · 32,054 delays · 2,187 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

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

Worst times to cross today

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

About this crossing

Billingshurst is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Horsham–Pulborough line (Sussex route · ELR TBH1). 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?

Our accuracy measurement doesn't cover this crossing yet. Reports from people at the crossing are the ground truth here. How we measure →

Is this right?