Bridlington South Bay polluted by sewage 90 times in 2022 - lasting 162 hours

© OpenStreetMap contributors
Contains OS Data © Crown copyright & database right 2021-2022
© Top of the Poops 2021-2023
Totals for Bridlington South Bay in 2022
3 Sites polluted by Yorkshire Water
90 sewage dumps
162 h duration
That's 6.75 days. 1.7 times a week, on average
How does Bridlington South Bay compare?

Bridlington South Bay was the #145 most polluted bathing area in England & Wales, by duration of sewage overflows, as reported by the water companies

Local Constituency

Pollution Summary 2022

Here are all the reported sewage overflow totals for Bridlington South Bay in 2022.

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.

Accuracy Warning 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.

Other CSOs 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 %
Yorkshire Water North Sea BRIDLINGTON STW 71 133 99.9
Yorkshire Water North Sea BRIDLINGTON STW 14 25 100
Yorkshire Water North Sea HILDERTHORPE ROAD CSO 5 3 100
Yorkshire Water North Sea BELGRAVE ROAD CSO 0 0 100

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.