CCTV-monitored manual barrier level crossing on the Wessex route (ELR BML2).
Information only — always follow the signals and barriers at the crossing. Predictions may be wrong.
| 11:02 | ❓ 0B45 | Eastleigh East Yard → Marchwood MOD GBRf Down (E → W) | no show |
| 11:02 | 🚛 6O45 | Kineton MOD GBRf → Marchwood MOD GBRf Down (E → W) | no show |
| 11:02 | 🚛 6O45 | Bicester MOD GBRf → Marchwood MOD GBRf Down (E → W) | no show |
| 11:04 | 🚄 1W54 | Weymouth → London Waterloo Up (W → E) | passed |
| 11:06 | 🚆 2B21 | Southampton Central → Bournemouth Down (E → W) | on time |
| 11:09 | 🚄 1M42 | Bournemouth → Manchester Piccadilly Up (W → E) | approaching |
| 11:10 | 🚃 5B39 | Wimbledon Park Depot Sidings → Bournemouth T.&R.S.M.D Down (E → W) | no show |
| 11:24 | 🚄 1W12 | Weymouth → London Waterloo Up (W → E) | +1 min |
| 11:34 | 🚄 1W61 | London Waterloo → Weymouth Down (E → W) | +4 min |
| 11:40 | ❓ 0B23 | Marchwood M.O.D. → Eastleigh East Yard Up (W → E) | sched |
On today’s timetable, Totton crossing is predicted to be closed for about 8 h 6 min between 06:00 and 22:00, across roughly 108 closures. The longest single predicted closure is 9 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: 7.4 min (10:04–10:11, 3 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:59–09:59 in the morning and around 16:29–17:29 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
Totton is a cctv-monitored manual barrier crossing (CCTV) on the Southampton M.C.T. EWS–Brockenhurst line (Wessex route · ELR BML2). 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 944 trains through this crossing.
99.9% of observed passes were being warned about on this page when they passed, and 99.7% of the warnings we could verify came true.
Typical timing error was ±132s (9 in 10 within 295s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.