Wagon Lane level crossing

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

predicted
OPEN
for 18 min

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

next: πŸš† in 19 min Β· 1 min late

Next 30 min

OPEN 09:59–10:17 18m
CLOSED 10:17–10:19 2m
OPEN 10:19–10:33 β†’ 15m
Under the hood
Thu 22 Oct Β· 09:59
Today Tomorrow

Trains in window

10:17 πŸš› 6Y93 Purley Foster Yeoman β†’ Cliffe Brett Marine Up (N β†’ S) no show
10:18 πŸš† 2T22 Strood β†’ Paddock Wood Up (N β†’ S) +1 min
10:29 ❓ 0Y21 Hoo Junction Up Yard β†’ Tonbridge West Yard GBRf Down (S β†’ N) sched
πŸš†Passenger πŸš›Freight ❓Other
now 09:59:55 Β· 86 avg Β· 3 in window
live observation: 1 up Β· 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,174 active Β· 31,699 delays Β· 1,963 cancelled Β· 9 reconnects
Nearby crossings

All 234 crossings in Southern β†’

About this crossing

How often it closes

On today’s timetable, Wagon Lane crossing is predicted to be closed for about 2 h 16 min between 06:00 and 22:00, across roughly 53 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: 2.5 min (08:45–08:47, 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:16–08:16 in the morning and around 20:33–21:33 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 on Wagon Lane in Paddock Wood, Kent.

Wagon Lane is a automatic half-barrier crossing (AHB) on the Paddock Wood Keylands Sdgs–Paddock Wood 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.

How accurate is this forecast?

We score this page against what actually happened on the railway: over the last 7 days that covered 469 trains through this crossing.

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

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

Full accuracy report β†’

Is this right?