Halbeath level crossing

CCTV-monitored manual barrier level crossing on the Scotland route (ELR CWH1).

predicted
OPEN
for 6 min

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

next: 🚆 in 9 min · on time

Next 30 min

OPEN 06:48–06:54 6m
CLOSED 06:54–06:57 3m
MAY OPEN 06:57–06:59 2m
CLOSED 06:59–07:02 3m
OPEN 07:02–07:14 13m
CLOSED 07:14–07:18 → 3m
Under the hood
Tue 06 Oct · 06:48
Today Tomorrow

Trains in window

06:57 🚆 2G51 Edinburgh → Leven Down (W → E) approaching
07:02 🚄 1L60 Perth → Edinburgh Up (E → W) on time
07:18 🚆 2G32 Glenrothes with Thornton → Edinburgh Up (E → W) active
🚄Express passenger 🚆Passenger
now 06:48:06 · 82 avg · 3 in window
live observation: 3 up · 1 down
timetable cif full+upd 2026-10-05..2026-10-07
fetched 02:08:18
trust 33,340 active · 31,668 delays · 1,672 cancelled · 0 reconnects
Nearby crossings

All 113 crossings in Scotland's Railway →

About this crossing

How often it closes

On today’s timetable, Halbeath crossing is predicted to be closed for about 4 h 28 min between 06:00 and 22:00, across roughly 51 closures. The longest single predicted closure is 7 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: 3.2 min (23:59–00:02, 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 07:54–08:54 in the morning and around 19:49–20:49 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Halbeath is a cctv-monitored manual barrier crossing (CCTV) on the Inverkeithing–Cowdenbeath line (Scotland route · ELR CWH1). A signaller monitors the crossing, confirms it is clear, and lowers the barriers ahead of each train. 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 501 trains through this crossing.

100.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 ±87s (9 in 10 within 137s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?