Murton (County Durham)

Polluted by sewage 58 times in 2024 lasting 332 hours

© OpenStreetMap contributors
Contains OS Data © Crown copyright & database right 2021-2024
© Top of the Poops 2021-2024

Select Another Place

Select the locality from the drop-down
✔ means we have live data

Totals for Murton (County Durham) in 2024

6 Sites polluted by Northumbrian Water
58 sewage dumps
332 hours duration
That's 13.83 days. 1.1 times a week, on average

Change Over Time

We need your support!

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 Now

Pollution Summary 2024

Here are all the reported sewage overflow totals for Murton (County Durham) 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 all the declared CSOs appeared to have monitoring enabled for more than 50% of the year

Company Waterway Site Sewage Dumps Duration (Hours) Reporting %
Northumbrian Water Dalton Burn DALTON RETAIL PARK CSO 28 303 100
Northumbrian Water Dalton Burn SEA VIEW STORAGE TANK 4 11 98.3
Northumbrian Water Dalton Dene BURNIP ROAD CSO 11 9 91.6
Northumbrian Water Murton Dene BARWICK STREET CSO 10 4 95.3
Northumbrian Water Dalton Burn B1285 STORAGE TANK 3 1 99.8
Northumbrian Water Dalton Burn HAWTHORNE CLOSE STORAGE TANK 2 1 90.2
Northumbrian Water Culverted Seaham Burn MURTON COMBINED SEWER OVERFLOW 0 0 67.3

Data Sources & Accuracy

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.