Gosberton level crossing

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

right now
OPEN
for 5 min
next: 🚛 in 8 min · 11 min early

Next 30 min

OPEN 01:11–01:16 5m
CLOSED 01:16–01:19 3m
OPEN 01:19–01:33 14m
CLOSED 01:33–01:36 4m
OPEN 01:36–01:45 → 8m
Under the hood
Fri 24 Jul · 01:11
Today Tomorrow

Trains in window

01:19 4L20 🚛 DONCIGB → FLXSSGB → from Sleaford -11 min
01:21 6V85 🚛 TINSLYY → ACTONTC → from Sleaford no show
01:36 4E19 🚛 THMSLGB → DONCIGB ← from Peterborough North Yd GBRf +17 min
01:36 4E52 🚛 WLSDEUT → HRTLPDF ← from Peterborough North Yd GBRf +6 min
🚛Freight
now 01:11:50 · 117 avg · 4 in window
lx berths down: L2/7061→L2/[email protected] · up: L2/LEUS→L2/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,086 active · 30,123 delays · 1,795 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Gosberton crossing is predicted to be closed for about 2 h 8 min between 06:00 and 22:00, across roughly 31 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: 3.2 min (00:20–00:23, 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 07:00–08:00 in the morning and around 16:57–17:57 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Gosberton 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 5 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 ±21s (9 in 10 within 99s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?