Picton level crossing

CCTV-monitored manual barrier level crossing on the East Coast route (ELR LEN3).

right now
CLOSED
for 2 min
next: 🚛 in 2 min · 5 min early

Next 30 min

CLOSED 01:11–01:13 2m
OPEN 01:13–01:38 25m
CLOSED 01:38–01:41 → 3m
Under the hood
Fri 24 Jul · 01:11
Today Tomorrow

Trains in window

01:12 6E16 🚛 KNOWFT → WLTNEFW ← from York -5 min
01:24 6M26 🚛 WLTNEFW → KNOWFT → from Eaglescliffe cancelled
01:41 6M62 🚛 TEESY → CORBBSC → from Eaglescliffe sched
🚛Freight
now 01:11:07 · 118 avg · 3 in window
lx berths up: Y1/L846→Y1/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,793 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Picton crossing is predicted to be closed for about 3 h 36 min between 06:00 and 22:00, across roughly 49 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 (01:01–01:04, 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 08:28–09:28 in the morning and around 16:55–17:55 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Picton is a cctv-monitored manual barrier crossing (CCTV) on the York–Eaglescliffe line (East Coast route · ELR LEN3). 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 1 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 ±233s (9 in 10 within 233s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?