Automatic half-barrier level crossing on the Anglia route (ELR BGK).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:53 | 🚄 1L30 | Birmingham New Street → Stansted Airport Up (NE → SW) | +3 min |
| 10:02 | 🚛 4M81 | Felixstowe North F.L.T. → Garston F.L.T. Down (SW → NE) | approaching |
| 10:16 | 🚄 1T21 | Kings Lynn → London Kings Cross Up (NE → SW) | +2 min |
| 10:17 | 🚄 1T14 | London Kings Cross → Kings Lynn Down (SW → NE) | +12 min |
| 10:22 | 🚄 1L05 | Sheffield → Norwich Up (NE → SW) | +4 min |
| 10:23 | 🚄 1K67 | Norwich → Stansted Airport Up (NE → SW) | on time |
| 10:25 | 🚄 1N49 | Stansted Airport → Birmingham New Street Down (SW → NE) | +9 min |
| 10:28 | 🚛 4M79 | Felixstowe South EWS → East Mids Gateway Tml DBC Down (SW → NE) | no show |
| 10:28 | 🚛 4M82 | Felixstowe North EWS → East Mids Gateway Tml DBC Down (SW → NE) | no show |
| 10:31 | 🚆 2L73 | Peterborough → Ipswich Up (NE → SW) | +2 min |
On today’s timetable, Kiln Lane crossing is predicted to be closed for about 6 h 5 min between 06:00 and 22:00, across roughly 127 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: 7.3 min (08:15–08:22, 4 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.
Closures cluster around 08:22–09:22 in the morning and around 20:03–21:03 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Kiln Lane in Ely, Cambridgeshire.
Kiln Lane is a automatic half-barrier crossing (AHB) on the Ely–March Up Yard GBRF line (Anglia route · ELR BGK). 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.
We score this page against what actually happened on the railway: over the last 7 days that covered 1,105 trains through this crossing.
98.6% of observed passes were being warned about on this page when they passed, and 99.1% of the warnings we could verify came true.
Typical timing error was ±21s (9 in 10 within 199s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.