TISHOMINGO, OK · Johnston County
MURRAY STATE COLLEGE Water System
Consumer Confidence Report status
MURRAY STATE COLLEGE 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 MURRAY STATE COLLEGE.
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)
- OK1010816
- System type
- Community Water System
- Population served
- 1,150
- Service connections
- 39
- Ownership
- state government
- Water source
- surface water (rivers, lakes, or reservoirs)
MURRAY STATE COLLEGE is one of 511 community water systems in Oklahoma in the 501 to 3,300 people size category, serving 1,150 people from surface water.
As of August 1, 2026, its federal record holds 8 entries between 1994 and 2015, all of which EPA lists as closed. Nothing has been added since 2015.
Of the 8, 5 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, the Stage 2 Disinfectants and Disinfection Byproducts Rule, and the Consumer Confidence Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedTotal Haloacetic Acids (HAA5)
October 1, 2015 – December 31, 2015
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2013 – September 25, 2015
ResolvedMonitoring and Reporting (DBP)
—CARBON, TOTAL
April 1, 2008 – June 30, 2008
ResolvedMonitoring and Reporting (DBP)
—TTHM
April 1, 2007 – June 30, 2007
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
April 1, 2007 – June 30, 2007
ResolvedMonitoring and Reporting (DBP)
—TTHM
October 1, 2006 – December 31, 2006
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2000 – April 17, 2002
ResolvedTreatment Technique (SWTR and GWR)
Health-basedSurface Water Treatment Rule
March 1, 1994 – March 31, 1994
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2015 – December 31, 2015 | Maximum Contaminant Level Violation, Average | Total Haloacetic Acids (HAA5) | Health-based | Resolved |
| July 1, 2013 – September 25, 2015 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| April 1, 2008 – June 30, 2008 | Monitoring and Reporting (DBP) | CARBON, TOTAL | — | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| October 1, 2000 – April 17, 2002 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| March 1, 1994 – March 31, 1994 | Treatment Technique (SWTR and GWR) | Surface Water Treatment Rule | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- August 15, 2019State Public Notification requested3 linked violations
- January 31, 2017State Compliance achieved12 linked violations
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achieved15 linked violations
- July 25, 2016State Compliance achieved4 linked violations
- July 25, 2016State Compliance achieved12 linked violations
- July 25, 2016State Compliance achieved5 linked violations
- July 25, 2016State Compliance achieved46 linked violations
- July 25, 2016State Compliance achieved5 linked violations
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achieved1 linked violation
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 25, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- April 7, 2016State Public Notification received1 linked violation
- March 14, 2016State Administrative/Compliance Order with penalty issued1 linked violation
- March 14, 2016State Public Notification requested1 linked violation
- September 25, 2015State Compliance achieved3 linked violations
- August 11, 2010State Compliance achieved2 linked violations
- May 13, 2010State Public Notification received2 linked violations
- May 3, 2010State Public Notification requested1 linked violation
- May 3, 2010State Administrative/Compliance Order with penalty issued1 linked violation
- January 15, 2010State Administrative/Compliance Order with penalty issued1 linked violation
- January 15, 2010State Public Notification requested1 linked violation
- November 23, 2009State Public Notification received7 linked violations
- October 5, 2009State Compliance achieved5 linked violations
- June 30, 2009State Violation/Reminder Notice5 linked violations
- June 30, 2009State Public Notification requested5 linked violations
- September 27, 2008State Compliance achieved4 linked violations
- April 18, 2008State Public Notification received4 linked violations
- March 18, 2008State Public Notification requested4 linked violations
- March 18, 2008State Administrative/Compliance Order with penalty issued4 linked violations
- September 26, 2007State Public Notification requested3 linked violations
- September 26, 2007State Violation/Reminder Notice1 linked violation
- September 1, 2007State Compliance achieved1 linked violation
- September 20, 2005State Administrative/Compliance Order with penalty issued8 linked violations
- September 20, 2005State Public Notification requested6 linked violations
- April 19, 2005State Public Notification requested14 linked violations
- September 5, 2003State Public Notification received3 linked violations
- August 5, 2003State Administrative/Compliance Order with penalty issued4 linked violations
- February 4, 2003State Public Notification requested1 linked violation
- April 17, 2002State Compliance achieved4 linked violations
- July 30, 2001State Administrative/Compliance Order with penalty issued2 linked violations
- October 19, 1995State Administrative/Compliance Order without penalty issued5 linked violations
Common questions
Is MURRAY STATE COLLEGE required to publish a Consumer Confidence Report?
- Yes. MURRAY STATE COLLEGE 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 MURRAY STATE COLLEGE’s next Consumer Confidence Report due?
- MURRAY STATE COLLEGE’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does MURRAY STATE COLLEGE have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for MURRAY STATE COLLEGE.
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
MURRAY STATE COLLEGE
580-371-2371
TISHOMINGO, OK 73460