CCTV-monitored manual barrier level crossing on the Anglia route (ELR BGK).
| 00:10 | 5H09 | 🚃 | CAMBCSS → CAMBNTH | ← from Cambridge Reception Sdgs | +7 min |
| 00:21 | 1T72 | 🚄 | KNGX → KLYNN | → from Ely | no show |
| 00:35 | 2C70 | 🚆 | KNGX → CAMBDGE | → from Ely | +5 min |
| 00:38 | 9S68 | 🚄 | BRGHTN → CAMBDGE | → from Ely | +3 min |
| 00:38 | 5H88 | 🚃 | ILFEMUD → CAMBCSN | → from Ely | no show |
| 00:44 | 2H72 | 🚆 | LIVST → CAMBDGE | → from Ely | -1 min |
On today’s timetable, Chesterton Junction crossing is predicted to be closed for about 13 h 1 min between 06:00 and 22:00, across roughly 79 closures. The longest single predicted closure is 35 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:05–00:08, 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 06:00–07:00 in the morning and around 15:35–16:35 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Chesterton Junction is a cctv-monitored manual barrier crossing (CCTV) on the Cambridge Reception Sdgs–Ely line (Anglia route · ELR BGK). 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 663 trains through this crossing.
99.8% of observed passes were being warned about on this page when they passed, and 95.4% of the warnings we could verify came true.
Typical timing error was ±61s (9 in 10 within 134s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.