CCTV-monitored manual barrier level crossing on the Kent route (ELR VIR).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 04:54 | 🚃 5P02 | Gillingham E.M.U.D. → Gillingham (Kent) Up (E → W) | active |
| 04:55 | 🚆 2U91 | Gillingham (Kent) → Sheerness-on-Sea Down (W → E) | approaching |
| 04:55 | ❓ 2K52 | ? → ? Up (E → W) | approaching |
| 05:01 | 🚃 5T06 | Gillingham E.M.U.D. → Gillingham (Kent) Up (E → W) | active |
| 05:21 | 🚄 1F05 | Faversham → St. Pancras International Up (E → W) | active |
On today’s timetable, Gillingham crossing is predicted to be closed for about 11 h 14 min between 06:00 and 22:00, across roughly 127 closures. The longest single predicted closure is 13 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: 6.2 min (00:25–00:31, 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.
Closures cluster around 07:47–08:47 in the morning and around 17:46–18:46 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Gillingham is a cctv-monitored manual barrier crossing (CCTV) on the Gillingham (Kent)–Up line (Kent route · ELR VIR). 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 1,685 trains through this crossing.
90.1% of observed passes were being warned about on this page when they passed, and 99.5% of the warnings we could verify came true.
Typical timing error was ±73s (9 in 10 within 169s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.