FloodRadar
Log inCreate free account
Every hour adds up.
Hours across separate overflows, from the records we hold.Loading the calculation…
Current year so far · previous full calendar year
Within 5 km of your chosen place · all companies and statuses
Latest reported starts among the overflows still reporting a discharge.
Loading stored reports…
Find the busiest hours. See the pattern through the week. Then explore how often rain came first.
Loading recorded spill starts…
Tap a square to see the recorded starts. Darker colours mean more starts.
Compare the rain recorded nearby before each spill began.
Of starts we could assess, how many followed at least 0.2 mm of rain?
This measures rain before recorded starts. It does not measure the chance of a spill whenever it rains, establish its cause, or show whether a discharge breached a permit. Rain at a nearby gauge can differ from rain over the sewer catchment.
See who is reporting spills, and where the gaps are. Select a figure to explore those sites on the map.
Loading the reports…
| Loading company reports… | ||||||
“Reported in 24h” includes sites spilling at the map’s timestamp. It is a count of overflow references, not individual spills, and overlaps the other columns. Nearby records with the same name can share a map pin; each source reference is still counted separately.
Coverage matters. These are the mapped sites FloodRadar holds, including Wales and Scotland. Unknown includes missing or stale feeds. Company registers and monitoring coverage differ, so counts alone are not a fair ranking of pollution or performance.
The same official returns and rankings as the existing sewage page. Compare companies, waterways and individual overflows.
Official annual returns are separate from the map’s recent status reports.
Register flags across the stored inventory, not a count of beaches or current spills. Flags can overlap and are not water-quality ratings.
Loading the annual figures…
Select a company or overflow to explore its full history.
Sewage in the water, dead fish or an unusual smell? Tell the environmental regulator what you saw, where and when. Photos can help.
Raise the issue with the company responsible.
Bring the wider picture back to your doorstep.
The useful part is knowing what was reported, when it was reported, and what is still unknown.
The company table counts each mapped overflow once. Spilling, not discharging, offline and unknown add up to the total. A recently ended spill belongs to “not discharging” now and can also appear in the 24-hour column.
Companies can send several start messages while an overflow is running. Those messages do not increase this map’s site count. “Spilling for” uses the feed’s reported status start; it is not silently extended to an earlier message.
Recorded starts and stops are shown in each overflow’s details. An end inferred from a later start is labelled “end not captured” and is not presented as a measured duration. A feed more than two hours old becomes unknown.
Illustrative messages from one overflow. Three updates still represent one site.
The stop is known. A continuous five-hour discharge needs evidence connecting the starts; this map does not invent it.
Rain adds context, not a verdict. Optional clouds mark gauges with at least 0.2 mm in a recent observed hour, passing FloodRadar’s freshness and sensor checks. They are gauge locations, not radar coverage or moving weather systems. Rainfall near an overflow does not prove why it discharged.
Open observed rain radarSource: water-company feeds held by FloodRadar. The 24-hour column uses the latest reported event start/end plus currently reported discharges; gaps in a feed can mean missed activity. Official annual totals follow their own reporting rules. Sources and licences · Annual sewage figures
FloodRadar helper · beta