Upton Lovell level crossing

Automatic half-barrier level crossing on the Wessex route (ELR SAL).

right now
OPEN
for 18 min
next: 🚛 in 19 min · 98 min late

Next 30 min

OPEN 01:12–01:30 18m
CLOSED 01:30–01:32 2m
OPEN 01:32–02:25 → 53m
Under the hood
Fri 24 Jul · 01:12
Today Tomorrow

Trains in window

01:32 6V68 🚛 CRAWFHH → MERHFHH → from Castle Cary +98 min
🚛Freight
now 01:12:46 · 194 avg · 1 in window
lx berths down: WW/D127→WW/[email protected] · up: WW/U127→WW/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,087 active · 30,124 delays · 1,796 cancelled · 0 reconnects
Nearby crossings

All 236 crossings in Southern →

About this crossing

How often it closes

On today’s timetable, Upton Lovell crossing is predicted to be closed for about 4 h 23 min between 06:00 and 22:00, across roughly 91 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.

Worst times to cross today

Closures cluster around 10:20–11:20 in the morning and around 13:44–14:44 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Upton Lovell is a automatic half-barrier crossing (AHB) on the Frome–Castle Cary line (Wessex route · ELR SAL). 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 252 trains through this crossing.

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

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

Full accuracy report →

Is this right?