Clock House level crossing

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

predicted
CLOSED
for 41s

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–09:59 41s
OPEN 09:59–10:14 15m
CLOSED 10:14–10:16 2m
OPEN 10:16–10:29 → 14m
Under the hood
Thu 22 Oct · 09:58
Today Tomorrow

Trains in window

09:59 🚄 1P24 Dover Priory → London Victoria (E) Up (S → N) on time
10:15 🚃 5U50 Faversham → Dover Priory Down (N → S) active
🚄Express passenger 🚃Empty stock
now 09:58:35 · 62 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active · 31,697 delays · 1,962 cancelled · 9 reconnects
Nearby crossings

All 234 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Clock House crossing is predicted to be closed for about 1 h 46 min between 06:00 and 22:00, across roughly 43 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: 3.0 min (07:20–07:23, 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 07:28–08:28 in the morning and around 18:30–19:30 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 near Faversham, Kent.

Clock House is a automatic half-barrier crossing (AHB) on the Faversham–Canterbury East line (Kent route · ELR FDM). 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 373 trains through this crossing.

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

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

Full accuracy report →

Is this right?