Moss Side level crossing

Automatic barrier locally monitored level crossing on the North West route (ELR KBS1).

predicted
OPEN
for 6 min

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

next: 🚆 in 7 min · 1 min late

Next 30 min

OPEN 09:58–10:04 6m
CLOSED 10:04–10:06 2m
OPEN 10:06–10:46 → 41m
Under the hood
Thu 22 Oct · 09:58
Today Tomorrow

Trains in window

09:49 🚆 2S54 Blackpool South → Preston Up (S → N) +2 min
10:05 🚆 2S63 Preston → Blackpool South Down (N → S) +1 min
🚆Passenger
now 09:58:41 · 39 avg · 2 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, Moss Side crossing is predicted to be closed for about 1 h 30 min between 06:00 and 22:00, across roughly 32 closures. The longest single predicted closure is 2 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: 1.5 min (03:46–03:47, 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:06–07:06 in the morning and around 16:05–17:05 in the afternoon. 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 Lytham Road in Moss Side, Lancashire, next to the station.

Moss Side is a automatic barrier locally monitored crossing (ABCL) on the Preston–Blackpool South line (North West route · ELR KBS1). 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 124 trains through this crossing.

99.2% 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 ±13s (9 in 10 within 111s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?