# Kennedale — water loss as filed

TWDB · PWS TX2200017 · TARRANT County · filings 2015–2023
https://municorn.us/water-loss/tx/kennedale/

## Summary

Kennedale reported **20.4% non-revenue water** in FY2023, higher than 62% of the 785 Texas systems that filed that year. At the utility's own reported water rates that is **$530,854 a year**, as computed in the filed audit itself. The figure is trending worse across the record.

**The filed balance closes**, to within 0.00% of reported system input.

## Filed history

| Year | Non-revenue water % | System input (MG) | Cost of losses/yr | Balance |
|---|---|---|---|---|
| 2023 | 20.4% | 629.9 | $530,854 | closed |
| 2022 | 11.5% | 461.6 | $191,000 | closed |
| 2021 | 7.8% | 360.7 | $61,471 | closed |
| 2020 | 11.3% | 400.5 | $89,370 | closed |
| 2019 | 14.5% | 366.3 | $99,541 | closed |
| 2018 | 20.0% | 415.1 | $148,959 | closed |
| 2017 | 17.7% | 359.6 | $109,205 | closed |
| 2016 | 14.4% | 348.2 | $48,373 | closed |
| 2015 | 11.9% | 363.9 | $54,941 | closed |

`closed` means the filed components sum to the filed input. `failed` means they do not, by the stated residual.
`insufficient` means the check could not run because figures are missing — never to be read as a pass.

## How the cost figure is built

Apparent loss is water delivered and never billed, so it is valued at the retail rate: revenue, recoverable inside a
budget year without capital work. Real loss is valued at variable production cost, because eliminating a leak saves
treatment and pumping rather than retail price. Where the filed audit carries its own cost of losses — as TWDB's
export does — those figures are used directly and no rate of ours enters the calculation.

## Source

Texas Water Development Board — historical water loss audit data. Retrieved 2026-08-09. https://www.twdb.texas.gov/conservation/data/water-loss-dashboard.asp

Volumes are normalized to million gallons on ingest; the export reports them in the unit each filing states.

Figures are as filed unless stated otherwise. If a number here is wrong it is wrong in the filing or wrong in
our reading of it, and both are worth knowing: ammar@municorn.us

---