Manual gate level crossing on the East Coast route (ELR ECM1).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:53 | 🚄 1E80 | Edinburgh → London Kings Cross Up (NW → SE) | +5 min |
| 09:53 | 🚄 1B82 | London Kings Cross → Lincoln Down (SE → NW) | +14 min |
| 09:57 | 🚄 1A12 | Leeds → London Kings Cross Up (NW → SE) | passed |
| 10:03 | 🚄 1S09 | London Kings Cross → Aberdeen Down (SE → NW) | approaching |
| 10:05 | 🚄 1H02 | London Kings Cross → Hull Down (SE → NW) | -2 min |
| 10:06 | 🚄 1E03 | Edinburgh → London Kings Cross Up (NW → SE) | approaching |
| 10:07 | 🚄 1D08 | London Kings Cross → Leeds Down (SE → NW) | +5 min |
| 10:13 | 🚄 1B83 | Lincoln → London Kings Cross Up (NW → SE) | +2 min |
| 10:23 | 🚄 1E04 | Edinburgh → London Kings Cross Up (NW → SE) | +8 min |
| 10:23 | 🚄 1S10 | London Kings Cross → Edinburgh Down (SE → NW) | +5 min |
| 10:31 | 🚄 1A92 | Beverley → London Kings Cross Up (NW → SE) | +8 min |
On today’s timetable, Woodcroft crossing is predicted to be closed for about 11 h 53 min between 06:00 and 22:00, across roughly 100 closures. The longest single predicted closure is 15 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.4 min (08:53–09:09, 5 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 09:22–10:22 in the morning and around 12:07–13:07 in the middle of the day. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Woodcroft Road near Etton, Cambridgeshire.
Woodcroft is a manual gate crossing (MGH) on the Peterborough North Yd GBRf–Grantham line (East Coast route · ELR ECM1). A signaller or crossing keeper closes the gates across the road 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,525 trains through this crossing.
99.9% of observed passes were being warned about on this page when they passed, and 99.4% of the warnings we could verify came true.
Typical timing error was ±8s (9 in 10 within 18s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.