Anglian Water · overflow AWS00516
Monitor offline
Recorded by the operator as TIDAL RIVER YARE.
The Environment Agency data shows this overflow's monitor (operator listed as Anglian Water) as offline (status timestamp in the public data: 27 Oct 2026 at 10:48 UTC); while offline the data cannot show whether it is spilling.
📍 52.60091°, 1.72673°
122
spill events
2h
cumulative discharge
4 min
longest single event
2026-05-13
first event on record
In the last 30 days this overflow recorded 1h of discharge. Across Anglian Water's 1,438 monitored overflows the median was 0h. This site is in the top 22% by 30-day spill duration.
10 other overflows discharge into the River Yare. 1 has its monitor offline. Combined recorded discharge in the last 30 days: 9h.
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
no rainfall data close enough
Rainfall comes from the nearest Environment Agency rain gauge within 10 km, using 15-minute readings rolled into hourly totals. Where a gauge is further away, or too many readings are missing, we say so rather than guess. Rain figures do not show whether a discharge was permitted; that is a matter for the regulator. How we keep the record.
What the water company itself reported to the Environment Agency’s annual returns for this overflow, year by year. Hours are the total reported discharge duration; monitor working is the share of the year the event monitor was operating (a figure of 0% may mean no usable monitoring data rather than no spills). These figures are the operator's own reporting, not our measurement, and our live record above begins on 6 May 2026.
| Year | Spills counted | Hours | Monitor working | Matched by |
|---|---|---|---|---|
| 2024 | 74 | 45h | 100% | hub id |
| 2025 | 64 | 43h | 100% | hub id |
2024, the operator's stated reason: "Data collection - Confirmed exceptional weather"
2025, the operator's stated reason: "Not asset maintenance - Hydraulic capacity"
Source: Environment Agency, Event Duration Monitoring storm overflow annual returns, all years. Matched to this overflow by hub id.
The nearest Environment Agency rain gauge, Acle, is 12.0 km from this overflow. It recorded 0.9 mm in the last 48 hours.
| Day (UTC) | Rain |
|---|---|
| 4 Nov 2026 | 0.0 mm |
| 3 Nov 2026 | 0.9 mm |
| 2 Nov 2026 | 3.0 mm |
| 1 Nov 2026 | 1.6 mm |
| 31 Oct 2026 | 0.0 mm |
| 30 Oct 2026 | 0.1 mm |
| 29 Oct 2026 | 0.2 mm |
Rainfall comes from 15-minute Environment Agency readings rolled into hourly and daily totals; the 48-hour figure rests on 188 of 192 possible readings. The gauge is 12.0 km from this overflow, so it may not match the rain at the site itself, and the latest day may be incomplete. Rain figures do not show whether a discharge was permitted; that is a matter for the regulator. How we keep the record.
AN-YAR270 · SALINE WATER - ESTUARINE SITES - NON BATHING/SHELLFISH
751 m away
No swimmer-relevant measurements available.
AN-GY533064 · SALINE WATER - DESIGNATED BATHING BEACHES
966 m away · last tested 7 weeks ago
AN-GY533074 · SALINE WATER - DESIGNATED BATHING BEACHES
994 m away · last tested 7 weeks ago
AN-YAR268 · SALINE WATER - ESTUARINE SITES - NON BATHING/SHELLFISH
1.3 km away
No swimmer-relevant measurements available.
AN-YAR297 · SALINE WATER - ESTUARINE SITES - NON BATHING/SHELLFISH
2.9 km away
No swimmer-relevant measurements available.
AN-GY532031 · SALINE WATER - DESIGNATED BATHING BEACHES
3.5 km away · last tested 7 weeks ago
The record above is verifiable from public Environment Agency and water-company data. Three official accountability channels — pre-filled with the evidence on this page.
If you can see foam, sewage debris, dead fish, or smell something wrong — submit a citizen report. Confirmed reports are added to the Truth Engine and strengthen the public record on this overflow.
📷 Report what you saw →The official complaints route. Most companies require submission through their web form rather than email — open the form, then paste the pre-filled letter.
Subject: Storm overflow AWS00516 on the TIDAL RIVER YARE: request for information Dear Anglian Water, I am writing about storm overflow AWS00516 on the TIDAL RIVER YARE. Environment Agency storm overflow monitoring data for overflow AWS00516 on the TIDAL RIVER YARE (operator listed as Anglian Water) records at least 50 spill events starting between 5 October 2026 and 4 November 2026; the 34 with a published end time total 49 min. The most recent recorded event started on 27 October 2026 at 10:46 UTC. As of 4 November 2026 at 11:57 UTC, the monitor for this overflow is reported as offline (status timestamp in the public data: 27 October 2026 at 10:48 UTC). While a monitor is reported offline, the public data cannot show whether the overflow is spilling. Further details from the public record: - Open automated data flags on River Truth for this overflow: 1 (comparisons between public datasets, not findings of fault) - On the River Yare, per the OS Open Rivers network (Ordnance Survey, Open Government Licence) - Location: 52.60091, 1.72673 - Sources: Environment Agency National Storm Overflow Hub and Water Quality Archive (Open Government Licence v3.0), cross-referenced via River Truth (https://rivertruth.co.uk/overflow/992) These figures are taken from public monitoring data as published and may be revised by the publisher. They are not a finding that any permit condition has been breached. [Add your personal context here, for example how you use this stretch of water.] Please could you tell me: 1. Whether the monitoring record summarised above is accurate and complete 2. What caused the recorded spill events 3. Why the monitor is reported as offline and when it is expected to report again 4. What work, if any, is planned at this overflow, and on what timeline 5. What measures are in place to reduce spills from this overflow in future [Delete if not applicable: I have copied the Environment Agency, Ofwat and my MP into this correspondence.] Yours faithfully, [Your name] [Your address] [Your customer reference if you are a Anglian Water customer]
This overflow sits in the Great Yarmouth constituency — currently represented by Rupert Lowe (Restore Britain). Click below to open WriteToThem with the letter copied to your clipboard — paste it into the message box.
Prefer to write to the MP for where you live? Enter your postcode and we'll redirect WriteToThem accordingly.
Subject: Constituent query: storm overflow AWS00516 on the TIDAL RIVER YARE Dear [your MP, WriteToThem will fill this in], I am writing as your constituent about public storm overflow monitoring data for our area. Environment Agency storm overflow monitoring data for overflow AWS00516 on the TIDAL RIVER YARE (operator listed as Anglian Water) records at least 50 spill events starting between 5 October 2026 and 4 November 2026; the 34 with a published end time total 49 min. The most recent recorded event started on 27 October 2026 at 10:46 UTC. As of 4 November 2026 at 11:57 UTC, the monitor for this overflow is reported as offline (status timestamp in the public data: 27 October 2026 at 10:48 UTC). While a monitor is reported offline, the public data cannot show whether the overflow is spilling. Further details from the public record: - Open automated data flags on River Truth for this overflow: 1 (comparisons between public datasets, not findings of fault) - On the River Yare, per the OS Open Rivers network (Ordnance Survey, Open Government Licence) - Location: 52.60091, 1.72673 - Sources: Environment Agency National Storm Overflow Hub and Water Quality Archive (Open Government Licence v3.0), cross-referenced via River Truth (https://rivertruth.co.uk/overflow/992) These figures are taken from public monitoring data as published and may be revised by the publisher. They are not a finding that any permit condition has been breached. [Add your personal context here, for example how you and your family use this stretch of water.] I would like to ask: 1. Whether you support strengthening the regulatory regime for storm overflows, and monitor coverage in particular 2. Whether you would raise the monitoring data for this overflow with the Secretary of State for Environment, Food and Rural Affairs, the Environment Agency or Ofwat Yours sincerely, [Your name] [Your address (WriteToThem requires a postal address to verify your constituency)]
MP details are looked up live from the UK Parliament Members API under the Open Parliament Licence v3.0. River Truth makes no claim about this MP's voting or advocacy record on water issues — they are shown solely as the elected representative for this constituency.
For active pollution incidents — dead fish, foam, sewage on the riverbank — the EA hotline operates 24/7 and triggers a recorded investigation.