CCTV-monitored manual barrier level crossing on the Wessex route (ELR SDP2).
Information only. Always follow the signals and barriers at the crossing. Predictions may be wrong.
| 09:49 | 🚄 1N14 | Brighton → Southampton Central Up (E → W) | +19 min |
| 09:55 | 🚄 1N17 | Southampton Central → Brighton Down (W → E) | +2 min |
| 10:01 | 🚄 1N16 | Brighton → Southampton Central Up (E → W) | approaching |
| 10:04 | 🚆 2E24 | Portsmouth & Southsea → Southampton Central Up (E → W) | +4 min |
| 10:05 | 🚄 1T17 | London Waterloo → Portsmouth Harbour Down (W → E) | +6 min |
| 10:13 | 🚄 1T34 | Portsmouth Harbour → London Waterloo Up (E → W) | on time |
| 10:13 | 🚆 2E17 | Southampton Central → Portsmouth & Southsea Down (W → E) | on time |
| 10:24 | 🚄 1N19 | Southampton Central → Brighton Down (W → E) | +1 min |
| 10:26 | 🚃 5Y00 | Southampton Central → Woking Down (W → E) | active |
| 10:29 | 🚄 1N18 | Brighton → Southampton Central Up (E → W) | +3 min |
On today’s timetable, Cosham crossing is predicted to be closed for about 9 h 35 min between 06:00 and 22:00, across roughly 98 closures. The longest single predicted closure is 11 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.3 min (05:39–05:45, 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:50–07:50 in the morning and around 20:53–21:53 in the evening. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.
The crossing is on Portsmouth Road in Cosham, Hampshire, next to the station.
Cosham is a CCTV-monitored manual barrier crossing (CCTV) on the Fareham–Portsmouth & Southsea line (Wessex route · ELR SDP2). 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 646 trains through this crossing.
100.0% of observed passes were being warned about on this page when they passed, and 99.6% of the warnings we could verify came true.
Typical timing error was ±23s (9 in 10 within 77s). This scores when trains pass: barrier movements aren't in the public feeds we can score against.