Daisyfield level crossing

Manual gate level crossing on the North West route (ELR DJH).

predicted
OPEN
for the next 30 min

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

Next 30 min

OPEN 09:58–10:36 → 38m
Under the hood
Thu 22 Oct · 09:58
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 09:58:42 · 59 avg · 0 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,173 active · 31,697 delays · 1,962 cancelled · 9 reconnects
Nearby crossings

All 148 crossings in North West and Central →

About this crossing

How often it closes

On today’s timetable, Daisyfield crossing is predicted to be closed for about 2 h 23 min between 06:00 and 22:00, across roughly 35 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: 6.6 min (06:30–06:37, 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 06:39–07:39 in the morning and around 18:44–19:44 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 Moss Street in Blackburn, Lancashire.

Daisyfield is a manual gate crossing (MGH) on the Blackburn–Clitheroe line (North West route · ELR DJH). A signaller or crossing keeper closes the gates across the road 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 514 trains through this crossing.

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

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

Full accuracy report →

Is this right?