Hawkesbury Lane level crossing

CCTV-monitored manual barrier level crossing on the West Coast South route (ELR CNN).

predicted
OPEN
for 6 min

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

next: 🚆 in 10 min · 2 min late

Next 30 min

OPEN 10:01–10:07 6m
CLOSED 10:07–10:10 3m
OPEN 10:10–10:43 → 32m
Under the hood
Thu 22 Oct · 10:01
Today Tomorrow

Trains in window

10:10 🚆 2G73 Leamington Spa → Nuneaton Down (SW → NE) +2 min
🚆Passenger
now 10:01:00 · 65 avg · 1 in window
live observation: 1 up · 1 down
timetable cif full+upd 2026-10-21..2026-10-23
fetched 02:08:22
trust 33,174 active · 31,699 delays · 1,966 cancelled · 9 reconnects
Nearby crossings

All 148 crossings in North West and Central →

About this crossing

How often it closes

On today’s timetable, Hawkesbury Lane crossing is predicted to be closed for about 2 h 14 min between 06:00 and 22:00, across roughly 33 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: 5.5 min (09:01–09:06, 2 trains), 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 13:18–14:18 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

The crossing is on Blackhorse Road in Exhall, Warwickshire.

Hawkesbury Lane is a CCTV-monitored manual barrier crossing (CCTV) on the Coventry Arena–Bedworth Ground Frame line (West Coast South route · ELR CNN). 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 292 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 ±2s (9 in 10 within 16s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?