Geilston level crossing

User-worked with stop lights level crossing on the Scotland route (ELR NEM7).

predicted
OPEN
for at least 2h

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

Next 30 min

OPEN 02:11–04:11+ 2h+
Under the hood
Mon 07 Sep · 02:11
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:11:30 · 89 avg · 0 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-09-06..2026-09-08
fetched 02:08:15
trust 48,282 active · 21,043 delays · 2,870 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Geilston crossing is predicted to be closed for about 1 h 39 min between 06:00 and 22:00, across roughly 61 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: 0.6 min (00:06–00:07, 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.

Worst times to cross today

Closures cluster around 10:25–11:25 in the morning and around 14:34–15:34 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Geilston is a user-worked with stop lights crossing (UWCMSL) on the Paisley Gilmour Street–Gourock line (Scotland route · ELR NEM7). 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 601 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 ±29s (9 in 10 within 192s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?