Automatic barrier locally monitored level crossing on the Kent route (ELR PWS1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 05:11 | 🚆 2T02 | Gillingham (Kent) → Tonbridge Up (N → S) | approaching |
| 05:16 | 🚆 2T05 | Tonbridge → Strood Up (N → S) | active |
On today’s timetable, Yalding crossing is predicted to be closed for about 2 h 7 min between 06:00 and 22:00, across roughly 42 closures. The longest single predicted closure is 4 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 (01:16–01:17, 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.
Closures cluster around 06:00–07:00 in the morning and around 19:41–20:41 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Yalding is a automatic barrier locally monitored crossing (ABCL) on the Paddock Wood Keylands Sdgs–Wateringbury line (Kent route · ELR PWS1). 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 360 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 98.0% of the warnings we could verify came true.
Typical timing error was ±39s (9 in 10 within 360s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.