Manually-controlled barrier level crossing on the Western route (ELR MLN3).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 17:58 | 🚆 2E23 | Penzance → Exeter St. David's Up (SW → NE) | approaching |
| 18:07 | 🚄 1C84 | London Paddington → Penzance Down (NE → SW) | approaching |
| 18:13 | ❓ 0C13 | Exeter Riverside N.Y. → St. Blazey SS Down (NE → SW) | cancelled |
| 18:24 | 🚆 2P24 | Penzance → Plymouth Up (SW → NE) | on time |
| 18:27 | 🚆 2C34 | Plymouth → Penzance Down (NE → SW) | -1 min |
On today’s timetable, Lostwithiel crossing is predicted to be closed for about 3 h 32 min between 06:00 and 22:00, across roughly 49 closures. The longest single predicted closure is 7 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: 6.9 min (10:22–10:29, 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 06:44–07:44 in the morning and around 17:28–18:28 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Lostwithiel is a manually-controlled barrier crossing (MCB/MB) on the Bodmin Parkway–Par line (Western route · ELR MLN3). 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 457 trains through this crossing.
98.9% of observed passes were being warned about on this page when they passed, and 99.3% of the warnings we could verify came true.
Typical timing error was ±7s (9 in 10 within 35s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.