Putney polluted by sewage 98 times in 2022 - lasting 273 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 Putney in 2022
4 Sites polluted by Thames Water
98 sewage dumps
273 h duration
That's 11.38 days. 1.9 times a week, on average
Live River Pollution Information (Updated 1 hour 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 Putney in 2022. Sometimes sewage can be being dumped for months at a time.

Company Waterway Site Sewage Dumps Duration (Hours) Reporting %
Thames Water River Thames PUTNEY BRIDGE STREET, LONDON 85 250 96.5
Thames Water Beverley Brook PRIORY LANE, MORTLAKE CSO 8 19 99.9
Thames Water River Wandle CSO AT MAPLETON ROAD/BRATHWAY ROAD 4 2 100
Thames Water Beverley Brook Road A3, Roehampton Vale 1 0 88.4
Thames Water River Wandle CSO AT DUNTSHILL ROAD 0 0 100
Thames Water River Wandle CSO AT PENWITH ROAD 0 0 100
Thames Water Beverley Brook Horn Way, 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.