Grove Ferry level crossing

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

predicted
OPEN
for 7 min

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

next: πŸš„ in 8 min Β· 1 min early

Next 30 min

OPEN 10:06–10:12 7m
CLOSED 10:12–10:14 2m
OPEN 10:14–10:32 18m
CLOSED 10:32–10:33 2m
OPEN 10:33–10:42 β†’ 9m
Under the hood
Sat 17 Oct Β· 10:06
Today Tomorrow

Trains in window

09:57 πŸš† 2G72 Ramsgate β†’ London Victoria (E) Up (E β†’ W) +1 min
10:13 πŸš„ 1J25 Margate β†’ St. Pancras International Up (E β†’ W) -1 min
10:33 πŸš† 2G18 London Victoria (E) β†’ Ramsgate Down (W β†’ E) +3 min
πŸš„Express passenger πŸš†Passenger
now 10:06:07 Β· 86 avg Β· 3 in window
live observation: 1 up Β· 1 down
timetable cif full+upd 2026-10-16..2026-10-18
fetched 02:08:22
trust 41,540 active Β· 36,868 delays Β· 2,800 cancelled Β· 0 reconnects
Nearby crossings

All 234 crossings in Southern β†’

About this crossing

How often it closes

On today’s timetable, Grove Ferry crossing is predicted to be closed for about 2 h 39 min between 06:00 and 22:00, across roughly 62 closures. The longest single predicted closure is 2 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: 2.1 min (07:09–07:11, 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:31–08:31 in the morning and around 12:45–13:45 in the middle of the day. 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 Grove Ferry Hill in Rivercroft, Kent.

Grove Ferry is a automatic half-barrier crossing (AHB) on the Canterbury West–Minster 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 634 trains through this crossing.

98.9% 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 Β±55s (9 in 10 within 144s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report β†’

Is this right?