Sevenscore level crossing

Automatic half-barrier level crossing on the Kent route (ELR ACR).

predicted
OPEN
for 20 min

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

next: 🚆 in 20 min · running

Next 30 min

OPEN 09:20–09:40 20m
CLOSED 09:40–09:41 1m
OPEN 09:41–09:44 2m
CLOSED 09:44–09:45 1m
OPEN 09:45–09:46 1m
CLOSED 09:46–09:47 1m
OPEN 09:47–09:53 → 6m
Under the hood
Mon 07 Sep · 09:20
Today Tomorrow

Trains in window

09:14 🚄 1L23 RamsgateAshford International Up (E → W) no show
09:41 🚆 2W28 RamsgateLondon Charing Cross Up (E → W) active
09:44 🚆 2R14 London Charing CrossRamsgate Down (W → E) +3 min
09:47 🚄 1L14 St. Pancras InternationalRamsgate Down (W → E) on time
🚄Express passenger 🚆Passenger
now 09:20:58 · 132 avg · 4 in window
live observation: 0 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 49,494 active · 28,102 delays · 3,115 cancelled · 0 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Sevenscore crossing is predicted to be closed for about 3 h 31 min between 06:00 and 22:00, across roughly 95 closures. The longest single predicted closure is 3 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: 1.5 min (00:38–00:40, 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 07:00–08:00 in the morning and around 18:18–19:18 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Sevenscore is a automatic half-barrier crossing (AHB) on the Deal–Ramsgate line (Kent route · ELR ACR). The approaching train itself triggers the closure at a fixed point on its approach. 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 425 trains through this crossing.

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

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

Full accuracy report →

Is this right?