# Quinlan — water loss as filed

TWDB · PWS TX1160007 · HUNT County · filings 2015–2024
https://municorn.us/water-loss/tx/quinlan/

## Summary

Quinlan reported **14.6% non-revenue water** in FY2024, higher than 39% of the 908 Texas systems that filed that year. At the utility's own reported water rates that is **$57,615 a year**, as computed in the filed audit itself. **The series is not stable enough to act on**: it moves 10.4 points a year against a Texas median of 5.8.

**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 | 14.6% | 62 | $57,615 | closed |
| 2023 | 9.6% | 59.3 | $35,211 | closed |
| 2022 | 21.6% | 66.6 | $66,026 | closed |
| 2021 | 11.9% | 59.8 | $7,747 | closed |
| 2019 | 16.2% | 55.8 | $14,148 | closed |
| 2018 | 17.0% | 62.9 | $42,114 | closed |
| 2017 | 6.0% | 63.2 | $10,617 | closed |
| 2015 | 36.1% | 61.5 | $49,361 | 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

---