# Belton — water loss as filed

TWDB · PWS TX0140002 · BELL County · filings 2016–2024
https://municorn.us/water-loss/tx/belton/

## Summary

Belton reported **18.6% non-revenue water** in FY2024, higher than 52% of the 908 Texas systems that filed that year. At the utility's own reported water rates that is **$369,043 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 | 18.6% | 1,332 | $369,043 | closed |
| 2023 | 17.0% | 1,391 | $377,319 | closed |
| 2022 | 13.4% | 1,396 | $349,733 | closed |
| 2020 | 14.7% | 1,233 | $305,797 | closed |
| 2019 | 12.1% | 1,113 | $237,793 | closed |
| 2018 | 12.7% | 1,117 | $240,772 | closed |
| 2017 | 12.7% | 1,086 | $231,606 | closed |
| 2016 | 15.4% | 1,062 | $215,190 | 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

---