# Midlothian — water loss as filed

TWDB · PWS TX0700005 · ELLIS County · filings 2015–2023
https://municorn.us/water-loss/tx/midlothian/

## Summary

Midlothian reported **17.0% non-revenue water** in FY2023, higher than 53% of the 785 Texas systems that filed that year. At the utility's own reported water rates that is **$826,586 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 | 17.0% | 1,941 | $826,586 | closed |
| 2022 | 16.9% | 1,664 | $532,909 | closed |
| 2021 | 27.7% | 1,368 | $614,013 | closed |
| 2020 | 19.8% | 1,217 | $285,924 | closed |
| 2019 | 19.8% | 1,081 | $261,282 | closed |
| 2018 | 15.5% | 886.1 | $156,154 | closed |
| 2017 | 13.9% | 814.9 | $149,154 | closed |
| 2015 | 14.1% | 807.3 | $181,121 | 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

---