Automatic half-barrier level crossing on the Wessex route (ELR RTJ2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 07:04 | 🚆 2R22 | Salisbury → Romsey Up (W → E) | -1 min |
| 07:13 | 🚄 1F06 | Portsmouth Harbour → Cardiff Central Down (E → W) | approaching |
| 07:23 | 🚄 1F03 | Bristol Temple Meads → Portsmouth Harbour Up (W → E) | approaching |
| 07:39 | 🚛 4M50 | Southampton M.C.T. → Basford Hall Yard Down (E → W) | sched |
| 07:42 | 🚛 6O52 | Westbury Tarmac → Chichester Recp. Up (W → E) | +27 min |
On today’s timetable, Dunbridge crossing is predicted to be closed for about 2 h 55 min between 06:00 and 22:00, across roughly 70 closures. The longest single predicted closure is 4 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: 1.9 min (05:52–05:54, 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:48–08:48 in the morning and around 19:38–20:38 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Dunbridge is a automatic half-barrier crossing (AHB) on the Romsey–Salisbury Reception Line line (Wessex route · ELR RTJ2). 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 614 trains through this crossing.
99.8% 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 ±3s (9 in 10 within 106s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.