Blackwood 2 level crossing

Automatic barrier locally monitored level crossing on the Scotland route (ELR KYL).

right now
OPEN
for at least 2h

Next 30 min

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

Trains in window

No trains in the next 30 minutes.
now 01:17:45 · 11 avg · 0 in window
lx berths up: IR/0361→IR/[email protected] · down: IR/0361→IR/[email protected] · down: IR/0421→IR/[email protected] · down: IR/0571→IR/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,126 delays · 1,796 cancelled · 0 reconnects
Nearby crossings

All 104 crossings in Scotland's Railway →

About this crossing

How often it closes

On today’s timetable, Blackwood 2 crossing is predicted to be closed for about 19 min between 06:00 and 22:00, across roughly 7 closures. The longest single predicted closure is 3 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.

Worst times to cross today

Closures cluster around 06:00–07:00 in the morning and around 14:33–15:33 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Blackwood 2 is a automatic barrier locally monitored crossing (ABCL) on the Achnashellach–Kyle of Lochalsh line (Scotland route · ELR KYL). 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 20 trains through this crossing.

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

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

Full accuracy report →

Is this right?