Flax Mill level crossing

Manually-controlled barrier with obstacle detection level crossing on the East Midlands route (ELR SPD1).

predicted
OPEN
for 17 min

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

next: 🚆 in 20 min · on time

Next 30 min

OPEN 07:11–07:28 17m
CLOSED 07:28–07:31 3m
OPEN 07:31–07:50 → 19m
Under the hood
Tue 06 Oct · 07:11
Today Tomorrow

Trains in window

07:07 🚆 2K01 Lincoln → Peterborough Up (N → S) +7 min
07:22 🚛 4E08 London Gateway GBRF → Wakefield Europort GBRF Down (S → N) no show
07:31 🚆 2K90 Peterborough → Doncaster Down (S → N) approaching
07:36 🚛 4L03 Doncaster Iport GBRF → Felixstowe South GBRF Up (N → S) no show
🚆Passenger 🚛Freight
now 07:11:06 · 86 avg · 4 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-05..2026-10-07
fetched 02:08:18
trust 33,379 active · 31,693 delays · 1,696 cancelled · 0 reconnects
Nearby crossings

All 866 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Flax Mill crossing is predicted to be closed for about 1 h 41 min between 06:00 and 22:00, across roughly 22 closures. The longest single predicted closure is 5 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 (05:59–06: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 06:00–07:00 in the morning and around 17:20–18:20 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Flax Mill is a manually-controlled barrier with obstacle detection crossing (MCBOD) on the Peterborough North Yd GBRf–Sleaford line (East Midlands route · ELR SPD1). 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 391 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 ±18s (9 in 10 within 52s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?