BURNET, TX · Burnet County
RIVER OAKS WATER SYSTEM Water System
Consumer Confidence Report status
RIVER OAKS WATER SYSTEM 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 RIVER OAKS WATER SYSTEM.
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)
- TX0270065
- System type
- Community Water System
- Population served
- 300
- Service connections
- 101
- Ownership
- privately owned
- Water source
- groundwater (wells)
RIVER OAKS WATER SYSTEM is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 300 people from groundwater.
As of August 1, 2026, its federal record holds 18 entries between 1981 and 2021, all of which EPA lists as closed. Nothing has been added since 2021.
Of the 18, 15 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 Total Coliform Rules.
Violation history
Monitoring and Reporting (DBP)
—Chlorine
October 1, 2021 – December 31, 2021
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
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
September 1, 1992 – September 30, 1992
ArchivedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 18, 1984 – July 17, 1985
ArchivedMaximum Contaminant Level Violation, Average
Health-basedFluoride
November 6, 1981 – November 5, 1982
ArchivedMaximum Contaminant Level Violation, Average
Health-basedFluoride
November 6, 1981 – December 5, 1981
Archived
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2021 – December 31, 2021 | 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 |
| September 1, 1992 – September 30, 1992 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| July 18, 1984 – July 17, 1985 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Archived |
| November 6, 1981 – November 5, 1982 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Archived |
| November 6, 1981 – December 5, 1981 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- February 27, 2026State Formal Notice of Violation issued6 linked violations
- January 29, 2026State Compliance achieved6 linked violations
- October 20, 2025State Public Notification requested10 linked violations
- May 22, 2025State Compliance achieved15 linked violations
- March 27, 2025State Public Notification requested5 linked violations
- June 5, 2024State Compliance achieved4 linked violations
- November 30, 2023State Public Notification requested4 linked violations
- September 28, 2021State Compliance achieved4 linked violations
- March 6, 2020State Administrative/Compliance Order with penalty issued12 linked violations
- February 4, 2020State Compliance achieved5 linked violations
- October 10, 2019State Compliance achieved3 linked violations
- October 10, 2019State Public Notification received3 linked violations
- September 30, 2019State Public Notification requested3 linked violations
- July 25, 2019State Public Notification requested4 linked violations
- March 15, 2019State Compliance achieved5 linked violations
- February 25, 2019State Public Notification received6 linked violations
- February 13, 2019State Public Notification requested7 linked violations
- October 24, 2017State Public Notification requested5 linked violations
- June 28, 2017State Public Notification received6 linked violations
- February 13, 2017State Violation/Reminder Notice4 linked violations
- February 13, 2017State Violation/Reminder Notice3 linked violations
- October 31, 2016State Compliance achieved4 linked violations
- October 31, 2016State Compliance achieved6 linked violations
- October 11, 2016State Compliance achieved4 linked violations
- October 7, 2016State Formal Notice of Violation issued43 linked violations
- September 14, 2016State Public Notification requested3 linked violations
- September 14, 2016State Violation/Reminder Notice10 linked violations
- September 14, 2016State Public Notification requested23 linked violations
- September 14, 2016State Public Notification requested11 linked violations
- September 14, 2016State Public Notification requested4 linked violations
- August 16, 2016State Violation/Reminder Notice4 linked violations
- July 19, 2016State Compliance achieved4 linked violations
- November 18, 2015State Public Notification requested4 linked violations
- June 22, 2015State Compliance achieved5 linked violations
- January 14, 2015State Public Notification requested4 linked violations
- July 17, 2014State Compliance achieved10 linked violations
- April 4, 2014State Compliance achieved3 linked violations
- April 4, 2014State Public Notification received3 linked violations
- November 14, 2013State Violation/Reminder Notice3 linked violations
- November 14, 2013State Violation/Reminder Notice3 linked violations
- November 14, 2013State Public Notification requested3 linked violations
- January 26, 2011State Violation/Reminder Notice6 linked violations
- January 21, 2011State Compliance achieved16 linked violations
- September 24, 2010State Public Notification requested3 linked violations
- December 2, 2009State Public Notification received2 linked violations
- October 1, 2009State Violation/Reminder Notice1 linked violation
- April 29, 2009State Public Notification received1 linked violation
- March 27, 2009State Violation/Reminder Notice1 linked violation
- July 19, 2007State Public Notification requested4 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 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
- May 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- November 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- October 1, 1979Federal issued Formal Notice of Violation2 linked violations
Common questions
Is RIVER OAKS WATER SYSTEM required to publish a Consumer Confidence Report?
- Yes. RIVER OAKS WATER SYSTEM 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 RIVER OAKS WATER SYSTEM’s next Consumer Confidence Report due?
- RIVER OAKS WATER SYSTEM’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does RIVER OAKS WATER SYSTEM have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for RIVER OAKS WATER SYSTEM.
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
ORTIZ, COLLEEN
512-756-6930
BURNET, TX 78611-5558