# Lake Palo Pinto Area Water Supply Corp — water loss as filed

TWDB · PWS TX1820069 · PALO PINTO County · filings 2017–2024
https://municorn.us/water-loss/tx/lake-palo-pinto-area-water-supply-corp/

## Summary

Lake Palo Pinto Area Water Supply Corp reported **32.2% non-revenue water** in FY2024, higher than 77% of the 908 Texas systems that filed that year. At the utility's own reported water rates that is **$30,055 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 |
|---|---|---|---|---|
| 2024 | 32.2% | 38.5 | $30,055 | closed |
| 2023 | 24.0% | 35.2 | $21,930 | closed |
| 2022 | 19.1% | 43.9 | $19,457 | closed |
| 2021 | 26.8% | 36.7 | $23,103 | closed |
| 2020 | 17.6% | 37.7 | $8,415 | closed |
| 2018 | 16.7% | 30.9 | $12,121 | closed |
| 2017 | 13.1% | 27.4 | $4,338 | 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

---