# Lake Livingston Holiday Shores 1 2 3 — water loss as filed

TWDB · PWS TX2040006 · SAN JACINTO County · filings 2015–2024
https://municorn.us/water-loss/tx/lake-livingston-holiday-shores-1-2-3/

## Summary

Lake Livingston Holiday Shores 1 2 3 reported **62.3% non-revenue water** in FY2024, higher than 98% of the 908 Texas systems that filed that year. At the utility's own reported water rates that is **$25,085 a year**, as computed in the filed audit itself. **The series is not stable enough to act on**: it moves 12.7 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 | 62.3% | 26.9 | $25,085 | closed |
| 2022 | 40.4% | 21.5 | $11,272 | closed |
| 2018 | 61.8% | 27.3 | $7,989 | closed |
| 2017 | 50.5% | 21 | $5,525 | closed |
| 2016 | 48.5% | 21.1 | $3,171 | closed |
| 2015 | 55.4% | 23.2 | $6,383 | 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

---