Geilston level crossing

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

right now
OPEN
for at least 2h

Next 30 min

OPEN 01:16–03:16+ 2h+
Under the hood
Fri 24 Jul · 01:16
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 01:16:30 · 255 avg · 0 in window
lx berths down: YO/Y581→YO/[email protected] · up: YO/Y582→YO/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,797 cancelled · 0 reconnects
About this crossing

How often it closes

On today’s timetable, Geilston crossing is predicted to be closed for about 5 h 51 min between 06:00 and 22:00, across roughly 190 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: 0.6 min (00:04–00:04, 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 06:08–07:08 in the morning and around 14:21–15:21 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 1,253 trains through this crossing.

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

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

Full accuracy report →

Is this right?