Is TEXAS COUNTY RWD #1 required to publish a Consumer Confidence Report?

Yes. TEXAS COUNTY RWD #1 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 TEXAS COUNTY RWD #1’s next Consumer Confidence Report due?

TEXAS COUNTY RWD #1’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

ADAMS, OK · Texas County

TEXAS COUNTY RWD #1 Water System

Consumer Confidence Report status

TEXAS COUNTY RWD #1 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 TEXAS COUNTY RWD #1.

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 Oklahoma’s official records. Always confirm current status with Oklahoma before making decisions based on this information.

System facts

System ID (PWSID): OK2007010
System type: Community Water System
Population served: 135
Service connections: 104
Ownership: local government
Water source: groundwater (wells)

TEXAS COUNTY RWD #1 is one of 1,277 community water systems in Oklahoma in the 500 or fewer people size category, serving 135 people from groundwater.

As of August 1, 2026, its federal record holds 6 entries between 1995 and 2015, all of which EPA lists as closed. Nothing has been added since 2015.

Of the 6, 3 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 Total Coliform Rules and the Lead and Copper Rule.

Violation history

Monitoring, Routine Major (TCR)
—
Coliform (TCR)
November 1, 2015 – November 30, 2015
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
October 1, 2015 – October 31, 2015
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
October 1, 2014 – October 31, 2014
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
September 1, 2011 – September 30, 2011
Resolved
Initial Tap Sampling for Pb and Cu
—
Lead and Copper Rule
October 1, 2009 – November 30, 2010
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
August 1, 1995 – August 31, 1995
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
November 1, 2015 – November 30, 2015	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
October 1, 2015 – October 31, 2015	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved
October 1, 2014 – October 31, 2014	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved
September 1, 2011 – September 30, 2011	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved
October 1, 2009 – November 30, 2010	Initial Tap Sampling for Pb and Cu	Lead and Copper Rule	—	Resolved
August 1, 1995 – August 31, 1995	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

June 2, 2025State Compliance achieved1 linked violation
September 19, 2022State Compliance achieved1 linked violation
February 3, 2021State Public Notification received1 linked violation
September 18, 2020State Public Notification requested1 linked violation
September 18, 2020State Violation/Reminder Notice1 linked violation
November 4, 2019State Public Notification received2 linked violations
December 28, 2016State Public Notification received1 linked violation
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
March 14, 2016State Violation/Reminder Notice1 linked violation
March 14, 2016State Public Notification requested1 linked violation
December 8, 2015State Public Notification requested1 linked violation
December 8, 2015State Violation/Reminder Notice1 linked violation
December 1, 2015State Compliance achieved12 linked violations
June 24, 2015State Compliance achieved1 linked violation
January 14, 2015State Violation/Reminder Notice1 linked violation
December 8, 2014State Public Notification received1 linked violation
December 4, 2014State Public Notification requested1 linked violation
December 4, 2014State Violation/Reminder Notice1 linked violation
October 31, 2014State Compliance achieved1 linked violation
March 28, 2013State Compliance achieved1 linked violation
February 13, 2013State Public Notification received1 linked violation
January 30, 2013State Administrative/Compliance Order with penalty issued1 linked violation
January 30, 2013State Public Notification requested1 linked violation
December 8, 2011State Public Notification received1 linked violation
November 7, 2011State Public Notification requested1 linked violation
November 7, 2011State Violation/Reminder Notice1 linked violation
September 30, 2011State Compliance achieved1 linked violation
July 6, 2011State Public Notification received1 linked violation
January 11, 2011State Public Notification requested1 linked violation
January 11, 2011State Violation/Reminder Notice1 linked violation
December 7, 2010State Public Notification received1 linked violation
November 30, 2010State Compliance achieved4 linked violations
November 16, 2010State Violation/Reminder Notice1 linked violation
November 16, 2010State Public Notification requested1 linked violation
November 16, 2010State Violation/Reminder Notice1 linked violation
November 16, 2010State Public Notification requested1 linked violation
August 11, 2010State Compliance achieved1 linked violation
March 1, 2010State Public Notification received1 linked violation
January 27, 2010State Public Notification requested1 linked violation
January 27, 2010State Violation/Reminder Notice1 linked violation
October 27, 2005State Compliance achieved2 linked violations
October 27, 2005State Public Notification received3 linked violations
September 20, 1995State Administrative/Compliance Order without penalty issued3 linked violations
July 18, 1991State Administrative/Compliance Order without penalty issuedgeneral compliance action — not tied to a specific violation on record

Common questions

Is TEXAS COUNTY RWD #1 required to publish a Consumer Confidence Report?: Yes. TEXAS COUNTY RWD #1 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 TEXAS COUNTY RWD #1’s next Consumer Confidence Report due?: TEXAS COUNTY RWD #1’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TEXAS COUNTY RWD #1 have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for TEXAS COUNTY RWD #1.
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

TEXAS COUNTY RWD #1

580-651-9460

ADAMS, OK 73901