Polluted by sewage 208 times in 2025 lasting 683 hours
Your local MP is Jim McMahon (Labour/Co-operative) - Find out more about their interests, donors, and voting at They Work For You
Please consider a one-off or small recurring donation. We need your help to keep this site going.
Donate NowHere are all the reported sewage overflow totals for Royton in 2025. Sometimes sewage can be being dumped for months at a time.
Reporting refers to how much of the time the monitoring was active. In this place all the declared CSO Combined Sewage Overflow - a device that, when operating, pours combined rainwater & sewage into a waterway s appeared to have monitoring enabled for more than 50% of the year
| Company | Waterway | Site | Sewage Dumps | Duration (Hours) | Reporting % |
|---|---|---|---|---|---|
| United Utilities | River Irk | ROYTON SETTLED STORM OVERFLOW | 34 | 329 | 92.3 |
| United Utilities | Clvrt Sec Of Sudden Brook | OLDHAM ROAD CSO 35027 | 84 | 240 | 99.7 |
| United Utilities | Plumpton Clough | SHEEPFOOT LANE CSO | 55 | 69 | 99.3 |
| United Utilities | Luzley Brrok | HOLDEN FOLD LANE CSO | 10 | 12 | 99.7 |
| United Utilities | River Beal Via Sws | STONELEIGH PARK CSO | 11 | 10 | 100 |
| United Utilities | Luzley Brook | COWLISHAW CSO | 4 | 9 | 98.8 |
| United Utilities | Plumpton Clough | WESTHULME HOSPITAL CSO | 3 | 5 | 100 |
| United Utilities | River Irk | FIR LANE COMBINED SEWER OVERFLOW | 4 | 4 | 99.5 |
| United Utilities | Plumpton Clough | BOUNDARY PARK ROAD CSO | 3 | 1 | 100 |
EDM (Event Duration Monitoring) data and Consented Discharges to Controlled Waters with Conditions from Environment Agency & Data Map Wales, and Scottish Water
Experimental derived data from Thames Water API, Some data may be missing or inaccurate. Live sewage data from Stream Water API
Uses Environment Agency rainfall data from the real-time data API (Beta) - Rainfall data is delayed by up to two days.
This website is intended to provide an accurate representation of the Environment Agency data. The data is hard to use, and thus some errors may have been made. If you find something that is incorrect, please raise an issue at the GitHub issues page and we'll endeavour to fix it quickly.
This project is not associated, approved or endorsed by any of the companies whose logos you see here.