St Stephens level crossing

CCTV-monitored manual barrier level crossing on the Kent route (ELR ACR).

predicted
OPEN
for 21 min

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

next: 🚄 in 24 min · running

Next 30 min

OPEN 04:55–05:16 21m
CLOSED 05:16–05:19 3m
OPEN 05:19–05:24 5m
CLOSED 05:24–05:27 → 3m
Under the hood
Mon 07 Sep · 04:55
Today Tomorrow

Trains in window

05:19 🚄 1J05 RamsgateSt. Pancras International Up (NE → SW) active
05:27 🚃 5R09 Ashford Down SidingsSandwich Down (SW → NE) active
🚄Express passenger 🚃Empty stock
now 04:55:10 · 91 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,718 active · 21,554 delays · 2,954 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, St Stephens crossing is predicted to be closed for about 4 h 40 min between 06:00 and 22:00, across roughly 63 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: 3.2 min (00:22–00:25, 1 train), 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:44–07:44 in the morning and around 19:49–20:49 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

St Stephens is a cctv-monitored manual barrier crossing (CCTV) on the Ashford Down Sidings–Ramsgate line (Kent route · ELR ACR). 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 598 trains through this crossing.

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

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

Full accuracy report →

Is this right?