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.
| 07:05 | 🚆 2E70 | Colchester → Peterborough Down (SW → NE) | +6 min |
| 07:07 | 🚄 1L01 | Nottingham → Norwich Up (NE → SW) | +5 min |
| 07:13 | 🚄 1T09 | Kings Lynn → London Kings Cross Up (NE → SW) | approaching |
| 07:13 | 🚄 1N43 | Stansted Airport → Birmingham New Street Down (SW → NE) | approaching |
| 07:18 | 🚆 2K58 | Cambridge → Norwich Down (SW → NE) | on time |
| 07:24 | 🚄 1T02 | London Kings Cross → Kings Lynn Down (SW → NE) | +19 min |
| 07:27 | 🚛 4E14 | Parkeston SS GBRF → Doncaster Iport GBRF Down (SW → NE) | +5 min |
| 07:28 | 🚄 1K59 | Lowestoft → Cambridge Up (NE → SW) | -1 min |
| 07:36 | 🚄 1T94 | London Kings Cross → Kings Lynn Down (SW → NE) | +3 min |
| 07:43 | 🚄 1R62 | Norwich → Liverpool Lime Street HL/ML Up (NE → SW) | +2 min |
| 07:44 | 🚄 1T11 | Kings Lynn → London Kings Cross Up (NE → SW) | on time |
On today’s timetable, Kiln Lane crossing is predicted to be closed for about 5 h 38 min between 06:00 and 22:00, across roughly 120 closures. The longest single predicted closure is 4 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.9 min (07:03–07:07, 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.
Closures cluster around 08:22–09:22 in the morning and around 13:55–14:55 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
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,089 trains through this crossing.
99.3% of observed passes were being warned about on this page when they passed, and 97.8% of the warnings we could verify came true.
Typical timing error was ±21s (9 in 10 within 359s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.