CCTV-monitored manual barrier level crossing on the East Coast route (ELR ECM1).
| 00:05 | 2C68 | 🚆 | KNGX → CAMBDGE | ← from Huntingdon | +7 min |
| 00:05 | 6L34 | 🚧 | HOOJUYD → WHTMLDC | ← from Huntingdon | no show |
| 00:12 | 1T97 | 🚄 | KLYNN → KNGX | → from Peterborough | on time |
| 00:26 | 5H88 | 🚃 | ILFEMUD → CAMBCSN | ← from Huntingdon | no show |
| 00:28 | 1T72 | 🚄 | KNGX → KLYNN | ← from Huntingdon | no show |
| 00:31 | 9J74 | 🚄 | HORSHAM → PBRO | ← from Huntingdon | +1 min |
| 00:34 | 2C70 | 🚆 | KNGX → CAMBDGE | ← from Huntingdon | +5 min |
| 00:35 | 1D36 | 🚄 | KNGX → LEEDS | ← from Huntingdon | +1 min |
| 00:36 | 9S68 | 🚄 | BRGHTN → CAMBDGE | ← from Huntingdon | +2 min |
| 00:38 | 6X34 | 🚧 | HOOJUYD → WHTMLDC | ← from Huntingdon | no show |
| 00:43 | 2H72 | 🚆 | LIVST → CAMBDGE | ← from Huntingdon | -1 min |
| 00:46 | 1E30 | 🚄 | EDINBUR → KNGX | → from Peterborough | -1 min |
On today’s timetable, Holme Lode crossing is predicted to be closed for about 14 h 49 min between 06:00 and 22:00, across roughly 40 closures. The longest single predicted closure is 69 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 (23:58–00:01, 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.
Closures cluster around 07:07–08:07 in the morning and around 16:06–17:06 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Holme Lode is a cctv-monitored manual barrier crossing (CCTV) on the Huntingdon–Peterborough line (East Coast route · ELR ECM1). 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.
We score this page against what actually happened on the railway — over the last 7 days that covered 7 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 ±39s (9 in 10 within 372s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.