The Yamuna’s pollution readings improved at several Delhi stretches after monsoon flows reached the river, but the data does not show recovery. Fecal coliform levels fell at some downstream locations in August, while dissolved oxygen improved marginally. Yet biochemical oxygen demand rose at most of those points, and the river remained unsuitable for bathing. The pattern exposes a central problem in Delhi’s river management: additional water can dilute and move accumulated sewage, but it cannot substitute for controlling the pollution entering the river.
Delhi Pollution Control Committee samples collected on August 5 recorded a sharp fall in fecal coliform at some downstream locations compared with the same period in 2025. At ITO Bridge, the level fell from 54,000 to 17,000 most probable numbers per 100 millilitres. At Okhla Barrage, it declined from 30,000 to 23,000. At Nizamuddin Bridge, the reading was almost unchanged at 13,000, while Asgarpur recorded 36,000 compared with 35,000 a year earlier.
These readings remained far above the limits cited in the report. The desirable limit was stated as 500 MPN per 10 millilitres and the standard as 200 MPN per 100 millilitres. The precise comparison is less important than the broad conclusion supported by the data: even after the monsoon contribution, sewage contamination remained extremely high at multiple points along the river.
The improvement followed the arrival of additional routine monsoon flow from July 9. In early July, the absence of adequate flow had left pollution levels broadly comparable with June. Once the river received more water, the increased volume appears to have diluted and transported some of the accumulated sewage load downstream.
That distinction matters. A river can record lower concentrations at a sampling point because more water has entered the system, without the underlying sources of pollution being removed. The August readings therefore show a change in the river’s immediate condition, not evidence that Delhi has solved its sewage or wastewater problem.
### The uneven signal in the water-quality data
Dissolved oxygen, another indicator of river health, also improved at the sampled locations. At ISBT Bridge, it rose from 2 milligrams per litre in August 2025 to 3 mg/l this year. At Nizamuddin, it increased from 4 to 4.6 mg/l, and at Okhla from 3.2 to 4 mg/l. Asgarpur recorded a smaller rise, from 2.3 to 2.6 mg/l.
The gains were still insufficient against the 5 mg/l standard required for bathing cited in the report. In other words, the river showed some signs of improved oxygen availability but remained below the relevant benchmark across these locations. The data points to partial dilution rather than a decisive improvement in ecological conditions.
The biochemical oxygen demand figures make the limitation clearer. BOD measures the oxygen required to treat organic matter in water. Higher BOD indicates a heavier organic load and greater pressure on the water’s available oxygen. In August, BOD increased at most downstream sites compared with the previous year: from 24 to 28 mg/l at ISBT, 14 to 18 mg/l at ITO, 7.2 to 12 mg/l at Nizamuddin, 7 to 10 mg/l at Okhla and 11 to 16 mg/l at Asgarpur.
Palla was the exception, where BOD improved from 3.7 to 3 mg/l. The contrast between falling fecal coliform at some points and rising BOD at most downstream locations is the most important feature of the dataset. It shows that no single indicator can describe the river’s condition. One measure may improve when flow rises, while another continues to reflect a substantial organic pollution burden.
The result is a river that can look better on one metric while remaining severely degraded on another. For residents and policymakers, that means a lower pollution concentration in a particular sample should not be treated as proof that the river is clean or safe for contact.
### Flow is an administrative issue, not only a weather event
The August data also draws attention to how the river’s flow is managed before it reaches Delhi. Bhim Singh Rawat of the South Asia Network on Dams, Rivers and People said the timing of sampling was important because floods during the season had been erratic and the river had not crossed even the warning level.
The maximum discharge received from the Hathnikund barrage this year was 63,109 cusecs on August 4, one day before the sampling. The river reached a maximum level of 204.09 metres on August 8, according to the report. That was lower than the warning level of 204.50 metres and the lowest reported maximum since August 2004 and July 2014, apart from the comparison years cited in the article.
These figures place Delhi’s water-quality readings within a larger flow-management system. The condition of the river inside the capital is influenced not only by local sewage discharge but also by the volume of water released upstream and the amount diverted into the East and West Uttar Pradesh canals at Hathnikund.
Rawat pointed to a change in the threshold for releasing water into the main river. During the 2023 Delhi floods, canal diversion was stopped once upstream inflow crossed 50,000 cusecs, allowing all available water to enter the river. He said the threshold for when water must be released into the main channel was later raised from 60,000 cusecs to 70,000 cusecs and subsequently to 1 lakh cusecs from 2024.
With flows crossing 60,000 cusecs only once or twice this season, canal operations were not meaningfully curtailed, according to Rawat. His argument is that the higher threshold delayed the additional water that could have provided the Yamuna with a stronger monsoon flush.
This does not establish that more water alone would have produced a clean river. It does, however, show that river health is partly shaped by decisions taken outside Delhi’s municipal boundaries. The volume available for dilution, transport and ecological functioning is connected to barrage operations, canal requirements and flood-management thresholds.
### The limits of a dilution-based improvement
The August readings expose the limits of relying on seasonal flow to improve the Yamuna. Monsoon water can temporarily alter concentrations, move pollutants and increase dissolved oxygen. But the higher BOD readings at most downstream sites indicate that organic pollution remained embedded in the system even after the river received additional flow.
This distinction is particularly important in a city where the river’s most visible pollution problem is often assessed through surface appearance or a small set of headline indicators. A temporary reduction in fecal coliform may create the impression of recovery, while the BOD data shows that the river continues to carry a substantial organic load.
The evidence supplied in the report does not identify the specific sewage quantities entering each stretch, nor does it provide a complete account of treatment capacity, operating sewage-treatment plants or individual drain outfalls. It therefore cannot establish which intervention would account for each change in the readings. What it does establish is that water-quality improvement was uneven across locations and indicators.
The geographic variation is also significant. ITO and Okhla saw substantial reductions in fecal coliform compared with the previous year, while Nizamuddin changed little and Asgarpur remained almost unchanged. Dissolved oxygen improved at all the listed downstream locations but stayed below the cited bathing standard. BOD rose everywhere except Palla.
That unevenness makes a strong case for reading the Yamuna as a connected but differentiated urban water system. Conditions change along the river as water moves through the city and receives, carries or dilutes different pollution loads. A citywide claim that the river has improved would therefore conceal the differences between monitoring points.
### What the data says about governance
The institutional lesson is that Delhi’s river problem cannot be reduced to one department or one season. The DPCC provides the water-quality evidence in this report, while upstream flow conditions are affected by the Hathnikund barrage and canal-management decisions. Local river conditions are consequently shaped by an interaction between pollution control, water releases and inter-state or regional water operations.
The data also separates two governance tasks that are often merged in public discussion. The first is managing the quantity and timing of water entering the river. The second is preventing untreated or inadequately treated sewage and other organic matter from reaching it. Monsoon flow can influence the first and temporarily mask the consequences of failure in the second, but it does not remove the need for source control.
The August sample provides a useful warning against treating a seasonal improvement as a permanent trend. Fecal coliform fell sharply at ITO, but remained at 17,000 MPN per 100 ml. At Okhla, the reading was still 23,000. At Nizamuddin and Asgarpur, the year-on-year change was limited. Meanwhile, BOD rose at nearly every listed downstream site.
The evidence therefore supports a measured conclusion. The Yamuna received some benefit from increased monsoon flow, but the benefit was partial, uneven and insufficient to make the river fit for bathing. The river’s condition continues to depend on both the water available to carry and dilute pollutants and the pollution load entering the system.
The next significant question is whether later monitoring shows sustained improvement across fecal coliform, dissolved oxygen and BOD, or whether the August readings remain a short-lived monsoon effect. Until the indicators improve together and remain within the relevant standards, the data does not support describing Delhi’s Yamuna as clean.
