Canfold Wood
Storm overflow run by Thames Water, discharging into Thornhurst Brook.
"Not discharging" means the company's monitor reports no discharge right now — not that the water is clean. The feed publishes status only; no discharge volume is measured.
Year by year
The Environment Agency's official annual returns, counted the EA's way (12/24-hour spills). 2026 is our own running count, the same way, from Thames Water's monitor log and the live feed. The official figure is published next spring.
A spill is the EA's 12/24-hour count: the first 12 hours of a discharge count as one, each further 24 hours with discharge as one more. "Monitor" is the share of that year the monitor was working, so a 0 beside a working monitor is a real zero; "no data" means the monitor produced no usable data that year — not zero. Years before 2024 are matched to this site by name and location, because the EA's site IDs changed that year; a monitor figure beside one of them means the outlet's permit confirms the match.
Downstream of this overflow
The next gauge downstream that the river map places is Flash Bridge (Cranleigh Waters), 7.9 km along the river.
A river gauge measures the level of the river; it does not measure this overflow's discharge, and a spill does not by itself explain a change there. Traced on OS Open Rivers (edition 2026-04), which leaves out many small channels.
Contains OS data © Crown copyright and database rights 2026.
What the 2025 return says
From Thames Water's annual return to the Environment Agency for this overflow.
"High spill threshold not met" means this overflow did not spill often enough to trigger the EA's formal high-spill review for that year. It is not a statement that the spills were harmless.
Discharges we have recorded
88 discharge periods since 28 Dec 2022. 87 of them come from Thames Water's own event-duration-monitoring records (from its open data service, Dec 2022 – Feb 2026); the live feed adds anything after that. The official annual count is the figure to quote.
-
7 h 30 min
-
1 h 0 min
-
2 h 15 min
-
3 h 15 min
-
10 h 0 min
-
4 h 45 min
-
5 h 30 min
-
13 h 0 min
-
5 h 30 min
-
1 d 4 h
Show 30 earlier (of 88)
| Started | Ended | Discharge time |
|---|---|---|
| 6 h 30 min | ||
| 12 h 15 min | ||
| 3 h 30 min | ||
| 30 min | ||
| 30 min | ||
| 4 h 15 min | ||
| 2 h 15 min | ||
| 45 min | ||
| 2 h 30 min | ||
| 30 min | ||
| 30 min | ||
| 1 h 0 min | ||
| 2 h 15 min | ||
| 30 min | ||
| 1 h 15 min | ||
| 2 h 15 min | ||
| 45 min | ||
| 1 h 30 min | ||
| 5 h 0 min | ||
| 30 min | ||
| 45 min | ||
| 7 h 45 min | ||
| 12 h 30 min | ||
| 2 h 30 min | ||
| 3 h 30 min | ||
| 7 h 0 min | ||
| 5 h 30 min | ||
| 2 h 30 min | ||
| 2 h 30 min | ||
| 22 h 0 min |
The year figures above use the EA's 12/24-hour counting method, so they are comparable with the official figures; the monitor log's 98 raw blocks were merged into 88 continuous discharge periods (gaps under 15 min joined).
What the feed showed
FloodRadar's own record of every change of state Thames Water's live feed has shown for this overflow, kept since : 5 states. The feed publishes its status now and its latest discharge, nothing older; the discharges above are read from this. It is here so the figures can be checked.
Show the last 5 states
| Seen | Status | Since | Latest discharge |
|---|---|---|---|
| Monitor offline | — | ||
| Not discharging | → | ||
| Discharging | → no end yet | ||
| Not discharging | → | ||
| Monitor offline | — |
Rain nearby last 30 days
Nearest live rain gauge: Rainfall gauge nr Cranleigh, 4.4 km away. Brown shading = when this overflow was discharging; ▼ = a discharge start.
Overflow shading is a timing match, not proof of cause — heavy rain and spills share a trigger. Times come from the water company’s event-duration monitor (site status only; no discharge volume is published).
Where it is
Tell me when this overflow discharges
One message when the company's monitor reports a new discharge here. At most one every 6 hours.
Setting this alert needs JavaScript. The alerts you already have are on your alerts page.
The alert repeats the monitor's status: whether the overflow is discharging, not how much or why. It can only tell you about a discharge that starts after you turn it on.
Concerned about this overflow?
Report pollution you can see or smell to the regulator straight away; the company handles complaints about the overflow itself.
Write to the MP
The Environment Agency's return places this overflow in the Dorking and Horley constituency. An MP can ask the company and the regulator questions on a constituent's behalf. These words carry the official figures; change them as you like.
The link opens Parliament's own "Find your MP", which gives the MP's name and how to write to them. FloodRadar sends nothing and keeps nothing you write. Check the constituency against your own address: an MP acts only for people who live in it.
Live status: © Thames Water storm overflow activity data, licensed under CC BY 4.0. Annual spill figures: Environment Agency Event Duration Monitoring return, © Environment Agency copyright and/or database right, Open Government Licence (OGL) v3.0. Spill-event history: Thames Water open data (its discharge alerts), © Thames Water Utilities Limited, used under its open data terms (https://data.thameswater.co.uk/s/terms-of-service). Changed by FloodRadar: each Start alert is paired with the Stop that follows it to make one discharge period; monitor-offline alerts are left out. Discharges marked "via Top of the Poops", come from Top of the Poops' record of the same company feed, used under CC BY-SA 4.0: the feed's own start and end times as its pages print them, not their derived hours. Times are shown in UK local time. FloodRadar republishes the monitor's status and the EA's figures; it does not measure discharges itself. Constituency and council area from the EA's return: contains OS data © Crown copyright and database right 2026.