CCTV-monitored manual barrier level crossing on the Anglia route (ELR EMP).
| 00:09 | 1T97 | 🚄 | KLYNN → KNGX | ← from March Up Yard GBRF | on time |
| 00:11 | 6L34 | 🚧 | HOOJUYD → WHTMLDC | → from Peterborough | no show |
| 00:29 | 5H88 | 🚃 | ILFEMUD → CAMBCSN | → from Peterborough | no show |
| 00:31 | 1T72 | 🚄 | KNGX → KLYNN | → from Peterborough | no show |
| 00:32 | 4L61 | 🚛 | GRSTNFT → FLXSNFL | → from Peterborough | no show |
| 00:34 | 2C70 | 🚆 | KNGX → CAMBDGE | → from Peterborough | +5 min |
| 00:37 | 9S68 | 🚄 | BRGHTN → CAMBDGE | → from Peterborough | +3 min |
| 00:38 | 4L10 | 🚛 | DONCBDY → FLXSNEW | → from Peterborough | no show |
| 00:44 | 2H72 | 🚆 | LIVST → CAMBDGE | → from Peterborough | on time |
| 00:46 | 6X34 | 🚧 | HOOJUYD → WHTMLDC | → from Peterborough | no show |
On today’s timetable, Funthams Lane crossing is predicted to be closed for about 12 h 21 min between 06:00 and 22:00, across roughly 81 closures. The longest single predicted closure is 33 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.
Closures cluster around 07:13–08:13 in the morning and around 12:20–13:20 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Funthams Lane is a cctv-monitored manual barrier crossing (CCTV) on the March Up Yard GBRF–Peterborough line (Anglia route · ELR EMP). 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 1 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 95.0% of the warnings we could verify came true.
Typical timing error was ±56s (9 in 10 within 56s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.