Chingford and Woodford Green polluted by sewage 155 times in 2022 - lasting 588 hours

© OpenStreetMap contributors
Contains OS Data © Crown copyright & database right 2021-2022
© Top of the Poops 2021-2023
✔ means we have experimental daily data for 2023
Totals for Chingford and Woodford Green in 2022
4 Sites polluted by Thames Water
155 sewage dumps
588 h duration
That's 24.5 days. 3 times a week, on average
Waterways in Chingford and Woodford Green
Live River Pollution Information (Updated 15 minutes ago)
On the map above you can see live river pollution information. Rivers likely to be impacted by sewage pollution are marked in brown. This is based on Thames Water live data API, and modelling by Dr Alex Lipp at Merton College, Oxford. More details on the methodology will be added soon.
Daily Data for 2023
     Monitoring Online      Monitoring Offline      Polluting      Potentially Polluting      Unknown
Daily data is experimental and data is not guaranteed to be accurate. Please inform us of any issue, we will fix.

Pollution Summary 2022

Here are all the reported sewage overflow totals for Chingford and Woodford Green in 2022. Sometimes sewage can be being dumped for months at a time.

Company Waterway Site Sewage Dumps Duration (Hours) Reporting %
Thames Water River Roding WORCESTER CRESCENT CSO 77 344 99.9
Thames Water Ching Brook BEECH HALL CRESCENT CSO 61 223 100
Thames Water River Roding CSO AT HIGH ROAD 13 13 100
Thames Water Lee Chingford Storm Tanks 4 7 99.8
Thames Water Ching Brook SURFACE WATER OUTFALL, WHITEHALL RO 0 0 0

Data Sources & Accuracy

EDM (Event Duration Monitoring) data and Consented Discharges to Controlled Waters with Conditions from Environment Agency & Data Map Wales

Experimental derived data from Thames Water API, Some data may be missing or inaccurate. This 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.