UMBARGER, TX · Randall County
UMBARGER COMMUNITY WATER SUPPLY Water System
Consumer Confidence Report status
UMBARGER COMMUNITY WATER SUPPLY must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.
As of August 1, 2026, EPA's federal records show no open violations for UMBARGER COMMUNITY WATER SUPPLY.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Texas’s official records. Always confirm current status with Texas before making decisions based on this information.
System facts
- System ID (PWSID)
- TX1910024
- System type
- Community Water System
- Population served
- 120
- Service connections
- 78
- Ownership
- local government
- Water source
- groundwater (wells)
UMBARGER COMMUNITY WATER SUPPLY is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 120 people from groundwater.
As of August 1, 2026, its federal record holds 17 entries between 2004 and 2022, all of which EPA lists as closed. Nothing has been added since 2022.
Of the 17, 14 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Stage 1 Disinfectants and Disinfection Byproducts Rule, inorganic chemicals, and the Public Notice Rule and Revised PN Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2022 – June 30, 2022
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
February 13, 2014 – November 15, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2009 – September 30, 2009
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2009 – March 31, 2009
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2007 – March 31, 2007
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2006 – December 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2006 – September 30, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2006 – June 30, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2006 – March 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2005 – December 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2005 – September 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2005 – June 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2005 – March 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2004 – December 31, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2004 – September 30, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2004 – June 30, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2004 – March 31, 2004
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2022 – June 30, 2022 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| February 13, 2014 – November 15, 2016 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2006 – September 30, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2006 – June 30, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2006 – March 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2005 – December 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2005 – September 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2005 – June 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2005 – March 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2004 – December 31, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2004 – September 30, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2004 – March 31, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 4, 2026State Compliance achieved3 linked violations
- June 1, 2026State Violation/Reminder Notice4 linked violations
- January 12, 2026State Violation/Reminder Notice4 linked violations
- August 15, 2025State Public Notification received4 linked violations
- August 14, 2025State Compliance achieved4 linked violations
- March 31, 2025State Public Notification requested5 linked violations
- March 9, 2022State Compliance achieved4 linked violations
- October 14, 2021State Compliance achieved4 linked violations
- September 30, 2021State Violation/Reminder Notice4 linked violations
- May 28, 2021State Compliance achieved4 linked violations
- December 17, 2020State Public Notification requested4 linked violations
- June 29, 2018State Formal Notice of Violation issued6 linked violations
- March 22, 2018State Public Notification requested3 linked violations
- December 7, 2017State Public Notification requested2 linked violations
- January 30, 2017State Compliance achieved3 linked violations
- November 29, 2016State Public Notification received5 linked violations
- November 29, 2016State Compliance achieved4 linked violations
- November 22, 2016State Compliance achieved3 linked violations
- November 15, 2016State Compliance achieved3 linked violations
- November 15, 2016State Public Notification received3 linked violations
- November 15, 2016State Public Notification received3 linked violations
- November 15, 2016State Public Notification received3 linked violations
- November 15, 2016State Compliance achieved2 linked violations
- November 15, 2016State Public Notification received3 linked violations
- October 12, 2016State Compliance achieved3 linked violations
- May 17, 2016State Violation/Reminder Notice3 linked violations
- March 31, 2016State Compliance achieved3 linked violations
- March 23, 2016State Violation/Reminder Notice3 linked violations
- November 5, 2015State Public Notification requested3 linked violations
- October 5, 2015State Violation/Reminder Notice4 linked violations
- June 26, 2015State Public Notification requested4 linked violations
- May 23, 2015State Administrative/Compliance Order with penalty issued29 linked violations
- January 14, 2015State Violation/Reminder Notice4 linked violations
- October 23, 2014State Public Notification requested4 linked violations
- October 17, 2014State Formal Notice of Violation issued21 linked violations
- July 2, 2014State Public Notification requested4 linked violations
- May 20, 2014State Violation/Reminder Notice2 linked violations
- May 20, 2014State Violation/Reminder Notice2 linked violations
- January 15, 2011State Public Notification received2 linked violations
- January 12, 2011State Public Notification requested1 linked violation
- August 19, 2009State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 27, 2009State Violation/Reminder Notice1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested2 linked violations
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- March 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
Common questions
Is UMBARGER COMMUNITY WATER SUPPLY required to publish a Consumer Confidence Report?
- Yes. UMBARGER COMMUNITY WATER SUPPLY is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is UMBARGER COMMUNITY WATER SUPPLY’s next Consumer Confidence Report due?
- UMBARGER COMMUNITY WATER SUPPLY’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does UMBARGER COMMUNITY WATER SUPPLY have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for UMBARGER COMMUNITY WATER SUPPLY.
What is a Consumer Confidence Report?
- A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.
Contact
STOCKER, JEFF
Phone not on record
UMBARGER, TX 79091-0014