Polluted by sewage 57 times in 2025 - lasting 278 hours
Monitoring fell below 50% in some locations so could be more
Lyme Regis Church Cliff Beach was the #107 most polluted bathing area in England & Wales, by duration of sewage overflows, as reported by the water companies
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 Lyme Regis Church Cliff Beach in 2025.
We use data from the water companies, but we are seeing many anomalies that make us believe that bathing location information is quite poor. The situation is likely far worse than reported here.
If the locations of the sewage outlets look a bit unusual, it is likely that the reporting of the data from the water company is in error. We rely on their data in order to draw these maps.
Other CSO Combined Sewage Overflow - a device that, when operating, pours combined rainwater & sewage into a waterway s may also be located nearby, however the water companies claim that these do not affect the water quality here.
| Company | Waterway | Site | Sewage Dumps | Duration (Hours) | Reporting % |
|---|---|---|---|---|---|
| South West Water | River Lim | HORN BRIDGE PSEO/CSO | 32 | 222 | 100 |
| South West Water | River Lim | MILL LANE CSO | 10 | 36 | 8.3 |
| South West Water | River Lim | GUN CLIFF PUMPING STATION | 4 | 18 | 100 |
| South West Water | River Lim | JERICHO CSO | 8 | 1 | 100 |
| South West Water | River Lim | GOSLINGS BRIDGE CSO | 3 | 0 | 95.8 |
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.