Cold Blow. level crossing

User-worked with stop lights level crossing on the Kent route (ELR BME2).

predicted
OPEN
for 25 min

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

next: πŸš„ in 25 min Β· on time

Next 30 min

OPEN 09:59–10:23 25m
CLOSED 10:23–10:24 50s
OPEN 10:24–10:28 4m
CLOSED 10:28–10:29 50s
OPEN 10:29–11:12 β†’ 44m
Under the hood
Thu 22 Oct Β· 09:59
Today Tomorrow

Trains in window

09:51 🚧 3W74 Tonbridge West Yard GBRf β†’ Tonbridge West Yard GBRf Down (SW β†’ NE) +5 min
10:24 πŸš„ 1L18 St. Pancras International β†’ Ramsgate Down (SW β†’ NE) on time
10:28 πŸš„ 1L27 Ramsgate β†’ Ashford International Up (NE β†’ SW) active
πŸš„Express passenger 🚧Engineering
now 09:59:04 Β· 55 avg Β· 3 in window
live observation: 2 up Β· 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active Β· 31,698 delays Β· 1,962 cancelled Β· 9 reconnects
About this crossing

How often it closes

On today’s timetable, Cold Blow. crossing is predicted to be closed for about 1 h 13 min between 06:00 and 22:00, across roughly 40 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: 1.4 min (08:34–08:36, 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:37–08:37 in the morning and around 19:26–20:26 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 Coldblow in Upper Walmer, Kent.

Cold Blow. is a user-worked with stop lights crossing (UWCMSL) on the Canterbury East–Deal line (Kent route · ELR BME2). 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 358 trains through this crossing.

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

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

Full accuracy report β†’

Is this right?