Pulford level crossing

Manually-controlled barrier with obstacle detection level crossing on the North West route (ELR WSJ2).

predicted
CLOSED
for 45s

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

next: 🚄 now · on time

Next 30 min

CLOSED 09:14–09:15 45s
OPEN 09:15–09:26 12m
CLOSED 09:26–09:29 3m
OPEN 09:29–09:47 → 18m
Under the hood
Tue 10 Nov · 09:14
Today Tomorrow

Trains in window

09:14 🚄 1D11 Birmingham International → Llandudno Junction Down (S → N) on time
09:29 🚄 1I10 Holyhead → Birmingham International Up (N → S) -1 min
🚄Express passenger
now 09:14:20 · 89 avg · 2 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-11-09..2026-11-11
fetched 02:08:15
trust 33,367 active · 31,601 delays · 1,884 cancelled · 0 reconnects
Nearby crossings

All 148 crossings in North West and Central →

About this crossing

How often it closes

On today’s timetable, Pulford crossing is predicted to be closed for about 2 h 46 min between 06:00 and 22:00, across roughly 39 closures. The longest single predicted closure is 6 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: 7.5 min (04:31–04:39, 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:32–07:32 in the morning and around 20:13–21:13 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 Dodleston Lane in Pulford, Cheshire.

Pulford is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Wrexham General–Bidston line (North West route · ELR WSJ2). An obstacle-detection system scans the crossing and confirms it is clear before the barriers lower automatically. 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 259 trains through this crossing.

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

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

Full accuracy report →

Is this right?