Various CSO's - Areas Of Carlton
Storm overflow run by Severn Trent Water, discharging into Ouse Dyke.
"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 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.
Other outlets here
Severn Trent Water runs 6 other overflows within 300 m that also discharge into Ouse Dyke. They share the sewer and the storm, so one outlet's figures are only part of what reaches the water.
This overflow (Mapperley - Hallam Road (CSO)): 0 spills in 2025. Distances are between the published outlet points. The names in brackets are Severn Trent Water's own, from its return.
What the 2025 return says
From Severn Trent Water's annual return to the Environment Agency for this overflow.
"High spill threshold not met" means this overflow did not spill often enough to trigger the EA's formal high-spill review for that year. It is not a statement that the spills were harmless.
Discharges we have recorded
No discharge has been recorded from the live feed for this overflow since we started following it. The official annual figure above is the record to rely on.
What the feed showed
FloodRadar's own record of every change of state Severn Trent Water's live feed has shown for this overflow, kept since : 1 state. 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 1 states
| Seen | Status | Since | Latest discharge |
|---|---|---|---|
| Not discharging | — |
Rain nearby last 30 days
Nearest live rain gauge: Rainfall gauge nr Carlton, 2.7 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.
Live status: © Severn Trent 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. 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.