CCTV-monitored manual barrier level crossing on the East Midlands route (ELR TSN1).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:05 | 🚆 2A10 | Nottingham → Matlock Up (NE → SW) | no show |
| 07:06 | 🚄 1D01 | Kettering → Nottingham Down (SW → NE) | on time |
| 07:10 | 🚆 2A47 | Matlock → Nottingham Down (SW → NE) | on time |
| 07:12 | 🚛 4M56 | Gloucester N.Y. GBRF → Beeston Sims Metals GBRf Down (SW → NE) | approaching |
| 07:13 | 🚄 1V04 | Nottingham → Cardiff Central Up (NE → SW) | approaching |
| 07:16 | 🚃 3A23 | Etches Park Sdgs → Beeston Sidings Down (SW → NE) | no show |
| 07:21 | 🚄 1B16 | Lincoln → London St. Pancras Up (NE → SW) | on time |
| 07:24 | 🚄 1D50 | Birmingham New Street → Nottingham Down (SW → NE) | on time |
| 07:30 | 🚆 2J49 | Ambergate → Cleethorpes Down (SW → NE) | on time |
| 07:35 | 🚃 5Z81 | Etches Park Sdgs → Nottingham Down (SW → NE) | sched |
| 07:38 | 🚆 2P52 | Nottingham → Leicester Up (NE → SW) | active |
On today’s timetable, Meadow Lane crossing is predicted to be closed for about 12 h 36 min between 06:00 and 22:00, across roughly 121 closures. The longest single predicted closure is 17 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: 16.3 min (06:04–06:20, 6 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:39–09:39 in the morning and around 13:58–14:58 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Meadow Lane is a cctv-monitored manual barrier crossing (CCTV) on the Trent Sidings–Nottingham line (East Midlands route · ELR TSN1). 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,548 trains through this crossing.
99.7% of observed passes were being warned about on this page when they passed, and 99.0% of the warnings we could verify came true.
Typical timing error was ±17s (9 in 10 within 272s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.