Station Road CSO
Storm overflow run by Northumbrian Water, discharging into River Wear.
"Not discharging" means the company's monitor reports no discharge right now — not that the water is clean. The feed publishes status only; no discharge volume is measured.
Year by year
The Environment Agency's official annual returns, counted the EA's way (12/24-hour spills). 2026 is our own running count, the same way, from the live feed: our own log of it begins on 28 February, and the discharges before that are Top of the Poops' record of the same feed. The feed reports only each overflow's latest discharge, so a discharge it moved past before we saw it end is counted as one spill with no hours: the hours are a floor. The official figure is published next spring.
A spill is the EA's 12/24-hour count: the first 12 hours of a discharge count as one, each further 24 hours with discharge as one more. "Monitor" is the share of that year the monitor was working, so a 0 beside a working monitor is a real zero; "no data" means the monitor produced no usable data that year — not zero. Years before 2024 are matched to this site by name and location, because the EA's site IDs changed that year; a monitor figure beside one of them means the outlet's permit confirms the match.
What the 2025 return says
From Northumbrian Water's annual return to the Environment Agency for this overflow.
This overflow spilled often enough to trigger the EA's high-spill review; the review line is the company's own stated reason.
Discharges we have recorded
777 discharge periods since 9 Jan 2020, 18 whose end the feed never gave. 642 of them come from Northumbrian Water's own event-duration-monitoring records (published on Stream, Jan 2020 – Dec 2025); the live feed adds anything after that. The official annual count is the figure to quote.
-
24 min
-
2 min
-
18 min
-
38 min
-
4 h 0 min
-
18 min
-
not captured
-
10 min
-
10 min
-
1 h 8 min
Show 30 earlier (of 777)
| Started | Ended | Discharge time |
|---|---|---|
| 30 min | ||
| 28 min | ||
| 14 min | ||
| 24 min | ||
| 8 min | ||
| 18 min | ||
| 42 min | ||
| 50 min | ||
| not captured, before | not captured | |
| 22 min | ||
| 44 min | ||
| not captured, before | not captured | |
| 26 min | ||
| 6 min | ||
| 26 min | ||
| 4 min | ||
| 58 min | ||
| not captured, before | not captured | |
| 2 min | ||
| 12 min | ||
| 24 min | ||
| 16 min | ||
| 30 min | ||
| 24 min | ||
| 26 min | ||
| 12 min | ||
| 22 min | ||
| 2 min | ||
| 26 min | ||
| 34 min |
The year figures above use the EA's 12/24-hour counting method, so they are comparable with the official figures; the monitor log's 888 raw blocks were merged into 777 continuous discharge periods (gaps under 15 min joined).
What the feed showed
FloodRadar's own record of every change of state Northumbrian Water's live feed has shown for this overflow, kept since : 12 states. The feed publishes its status now and its latest discharge, nothing older; the discharges above are read from this. It is here so the figures can be checked.
Show the last 12 states
| Seen | Status | Since | Latest discharge |
|---|---|---|---|
| Not discharging | → | ||
| Discharging | → no end yet | ||
| Not discharging | → | ||
| Not discharging | → | ||
| Not discharging | → | ||
| Discharging | → no end yet | ||
| Not discharging | → | ||
| Discharging | → no end yet | ||
| Discharging | → no end yet | ||
| Not discharging | → | ||
| Discharging | → no end yet | ||
| Not discharging | → |
Rain nearby last 30 days
Nearest live rain gauge: Rainfall gauge nr Washington, 2.5 km away. Brown shading = when this overflow was discharging; ▼ = a discharge start.
Overflow shading is a timing match, not proof of cause — heavy rain and spills share a trigger. Times come from the water company’s event-duration monitor (site status only; no discharge volume is published).
Where it is
Tell me when this overflow discharges
One message when the company's monitor reports a new discharge here. At most one every 6 hours.
Setting this alert needs JavaScript. The alerts you already have are on your alerts page.
The alert repeats the monitor's status: whether the overflow is discharging, not how much or why. It can only tell you about a discharge that starts after you turn it on.
Concerned about this overflow?
Report pollution you can see or smell to the regulator straight away; the company handles complaints about the overflow itself.
Write to the MP
The Environment Agency's return places this overflow in the Washington and Gateshead South constituency. An MP can ask the company and the regulator questions on a constituent's behalf. These words carry the official figures; change them as you like.
The link opens Parliament's own "Find your MP", which gives the MP's name and how to write to them. FloodRadar sends nothing and keeps nothing you write. Check the constituency against your own address: an MP acts only for people who live in it.
Live status: © Northumbrian Water storm overflow activity data, licensed under CC BY 4.0. Annual spill figures: Environment Agency Event Duration Monitoring return, © Environment Agency copyright and/or database right, Open Government Licence (OGL) v3.0. Storm-overflow spill events: © the respective water company, published on Stream (data.streamwaterdata.co.uk) under CC BY 4.0. Discharges marked "EA start/stop data": Environment Agency Event Duration Monitoring storm overflow start/stop detailed data, © Environment Agency copyright and/or database right 2026, Open Government Licence v3.0; the companies' monitor records as the EA received them, not verified by the EA. Discharges marked "via Top of the Poops", and this year's figures before 28 February, come from Top of the Poops' record of the same company feed, used under CC BY-SA 4.0: the feed's own start and end times as its pages print them, not their derived hours. Times are shown in UK local time. FloodRadar republishes the monitor's status and the EA's figures; it does not measure discharges itself. Constituency and council area from the EA's return: contains OS data © Crown copyright and database right 2026.