Anglian Water · overflow AWS00056
No active event
Recorded by the operator as Trib River Rhee. The outfall is 42 m from the River Cam on the Ordnance Survey river network, which is the river this page groups it under.
The monitor for overflow AWS00056 (operator listed as Anglian Water) reports no current spill. The data records 19 spill events totalling 2.1 h in the last 30 days.
📍 52.12706°, 0.03936°
“Rain gauge Bassingbourn, 7.8 km from this overflow, recorded 0.8 mm in the 24 hours and 0.8 mm in the 48 hours before this spill started.”
☂ Only 0.8 mm rainfall in the 24 h before this spill started (recorded at Bassingbourn, 7821 m away)
50
spill events
6h
cumulative discharge
59 min
longest single event
2026-06-03
first event on record
In the last 30 days this overflow recorded 2h of discharge. Across Anglian Water's 1,438 monitored overflows the median was 0h. This site is in the top 4% by 30-day spill duration.
2 other overflows discharge into the Trib River Rhee. Combined recorded discharge in the last 30 days: 0h.
0.8 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0.8 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0.8 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
2.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
2.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
7.4 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
7.4 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
7.4 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
5.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
5.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
5.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
5.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
5.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
2.4 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
3.2 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
0 mm rain in the 24 h before, gauge Bassingbourn, 7.8 km
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 | 60 | 105h | 100% | hub id |
| 2025 | 14 | 16h | 100% | hub id |
2024, the operator's stated reason: "High spill threshold not met"
2025, the operator's stated reason: "High spill threshold not met"
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, Bassingbourn, is 7.8 km from this overflow. It recorded 4.6 mm in the last 48 hours.
| Day (UTC) | Rain |
|---|---|
| 17 Oct 2026 | 1.8 mm |
| 16 Oct 2026 | 3.0 mm |
| 15 Oct 2026 | 0.0 mm |
| 14 Oct 2026 | 0.0 mm |
| 13 Oct 2026 | 0.8 mm |
| 12 Oct 2026 | 0.0 mm |
| 11 Oct 2026 | 0.0 mm |
Rainfall comes from 15-minute Environment Agency readings rolled into hourly and daily totals; the 48-hour figure rests on 184 of 192 possible readings. The gauge is 7.8 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.
Latest readings at the Environment Agency gauge "Burnt Mill", on the River Rhee, which is 3.3 km from this overflow.
These are the Environment Agency's own gauge readings at the named station, shown for context. The station measures the river, not this overflow, and a reading does not show whether a discharge occurred or was permitted. Trend compares the latest reading with the one nearest 24 hours earlier; a change of 5% or less is shown as steady. How we keep the record.
AN-30M22 · FRESHWATER - RIVERS
235 m away
No swimmer-relevant measurements available.
AN-LSN0090 · FRESHWATER - LAKES/PONDS/RESERVOIRS
1.8 km away
No swimmer-relevant measurements available.
AN-30M35 · FRESHWATER - RIVERS
1.9 km away
No swimmer-relevant measurements available.
AN-30M36 · FRESHWATER - RIVERS
1.9 km away
No swimmer-relevant measurements available.
AN-30M07 · FRESHWATER - RIVERS
2.5 km away · last tested 2 weeks ago
AN-30M25 · FRESHWATER - RIVERS
2.6 km away
No swimmer-relevant measurements available.
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 AWS00056 on the Trib River Rhee: request for information Dear Anglian Water, I am writing about storm overflow AWS00056 on the Trib River Rhee. Environment Agency storm overflow monitoring data for overflow AWS00056 on the Trib River Rhee (operator listed as Anglian Water) records 19 spill events starting between 18 September 2026 and 18 October 2026, totalling 2.1 h. The most recent recorded event started on 13 October 2026 at 19:05 UTC. As of 18 October 2026 at 01:27 UTC, the monitor does not report the overflow as 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 Cam, per the OS Open Rivers network (Ordnance Survey, Open Government Licence) - Location: 52.12706, 0.03936 - 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/42) 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. What work, if any, is planned at this overflow, and on what timeline 4. 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 South Cambridgeshire constituency — currently represented by Pippa Heylings (Liberal Democrat). 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 AWS00056 on the Trib River Rhee 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 AWS00056 on the Trib River Rhee (operator listed as Anglian Water) records 19 spill events starting between 18 September 2026 and 18 October 2026, totalling 2.1 h. The most recent recorded event started on 13 October 2026 at 19:05 UTC. As of 18 October 2026 at 01:27 UTC, the monitor does not report the overflow as 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 Cam, per the OS Open Rivers network (Ordnance Survey, Open Government Licence) - Location: 52.12706, 0.03936 - 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/42) 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.