Ingate Street level crossing

Automatic barrier locally monitored level crossing on the Anglia route (ELR ESK).

right now
OPEN
for at least 2h

Next 30 min

OPEN 02:05–04:05+ 2h+
Under the hood
Fri 24 Jul · 02:05
Today Tomorrow

Trains in window

No trains in the next 30 minutes.
now 02:05:47 · 35 avg · 0 in window
lx berths down: SX/2055→SX/[email protected] · up: SX/2056→SX/[email protected] · up: SX/2058→SX/[email protected] · up: SX/2060→SX/[email protected]
timetable cif full+upd 2026-07-22..2026-07-24
fetched 23:44:56
trust 33,100 active · 30,165 delays · 1,826 cancelled · 0 reconnects
Nearby crossings

All 867 crossings in Eastern →

About this crossing

How often it closes

On today’s timetable, Ingate Street crossing is predicted to be closed for about 59 min between 06:00 and 22:00, across roughly 18 closures. The longest single predicted closure is 3 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.

Worst times to cross today

Closures cluster around 06:45–07:45 in the morning and around 16:15–17:15 in the afternoon. Gaps between closures are longest outside those windows. Other days run a different timetable, so the peaks move.

About this crossing

Ingate Street is a automatic barrier locally monitored crossing (ABCL) on the Woodbridge–Oulton Broad South line (Anglia route · ELR ESK). 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.

How accurate is this forecast?

We score this page against what actually happened on the railway — over the last 7 days that covered 232 trains through this crossing.

97.0% 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 524s). This scores when trains pass — barrier movements aren't in the public feeds we can score against.

Full accuracy report →

Is this right?