Automatic full-barrier locally monitored level crossing on the Scotland route (ELR ARH).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 10:50 | 🚆 2F62 | Ardrossan Harbour → Glasgow Central High Level Up (SW → NE) | active |
| 11:04 | 🚆 2F59 | Glasgow Central High Level → Ardrossan Harbour Down (NE → SW) | approaching |
On today’s timetable, Ardrossan Princes Street crossing is predicted to be closed for about 1 h 30 min between 06:00 and 22:00, across roughly 34 closures. The longest single predicted closure is 2 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: 4.0 min (00:04–00:08, 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 07:04–08:04 in the morning and around 16:41–17:41 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Princes Street in Ardrossan, North Ayrshire, next to Ardrossan Town station.
Ardrossan Princes Street is a automatic full-barrier locally monitored crossing (AFBCL) on the Ardrossan South Beach–Ardrossan Harbour line (Scotland route · ELR ARH). 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 338 trains through this crossing.
78.1% of observed passes were being warned about on this page when they passed, and 100.0% of the warnings we could verify came true.
Typical timing error was ±71s (9 in 10 within 698s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.