Polluted by sewage 46 times in 2024 lasting 198 hours
Monitoring was disabled in some locations, so could be more
We managed to raise £150 in 2024. That's not enough to keep the site running. Please consider a one-off or small recurring donation.
Donate NowHere are all the reported sewage overflow totals for Coatbridge in 2024. 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 locality 6 of the total 10 CSO locations had reporting enabled for less than half the year. Of these 6 had zero reporting.
| Company | Waterway | Site | Sewage Dumps | Duration (Hours) | Reporting % |
|---|---|---|---|---|---|
| Scottish Water | North Burn | COATBRIDGE CROMLET DR CSO 2020 NS739660 | 16 | 161 | 74.79 |
| Scottish Water | North Burn | AIRDRIE, WHINHALL RD/BURNFOOT RD CSO | 30 | 37 | 100.27 |
| Scottish Water | Gartsherrie Burn | COATBRIDGE, 50M E/O HERITAGE WAY CSO | 0 | 0 | 0 |
| Scottish Water | Gartsherrie Burn | COATBRIDGE, BELOW RAILWAY BRIDGE/BANK ST | 0 | 0 | 0 |
| Scottish Water | North Burn | COATBRIDGE, CAMERON STREET CSO | 0 | 0 | 0 |
| Scottish Water | Burginsholm Burn | DRUMPELLIER PARK CSO 2010 NS720652 | 0 | 0 | 0 |
| Scottish Water | Gartsherrie Burn | GARTSHERRIE ROAD SST CSO | 0 | 0 | 0 |
| Scottish Water | Luggie Burn | KIRKWOOD STREET CSO 2008 NS722644 | 0 | 0 | 99.73 |
| Scottish Water | Luggie Burn | LANGLOAN PARK CSO 2008 NS727644 | 0 | 0 | 94.52 |
| Scottish Water | Shirrel Burn | NORTH ROAD BRIDGE BELLSHILL CSO | 0 | 0 | 0 |
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.