BELGRADE, MT · Gallatin County
RIVER ROCK COUNTY WATER AND SEWER DIST Water System
Consumer Confidence Report status
RIVER ROCK COUNTY WATER AND SEWER DIST 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 ROCK COUNTY WATER AND SEWER DIST.
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 Montana’s official records. Always confirm current status with Montana before making decisions based on this information.
System facts
- System ID (PWSID)
- MT0004082
- System type
- Community Water System
- Population served
- 4,200
- Service connections
- 1,204
- Ownership
- privately owned
- Water source
- groundwater (wells)
RIVER ROCK COUNTY WATER AND SEWER DIST serves 4,200 people from groundwater, placing it in the 3,301 to 10,000 people size category.
As of August 1, 2026, its federal record holds 3 entries between 2014 and 2020, all of which EPA lists as closed. Nothing has been added since 2020.
All 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 Stage 2 Disinfectants and Disinfection Byproducts Rule and synthetic organic chemicals.
Violation history
Monitoring, Regular
—Diquat
January 1, 2020 – December 31, 2022
ResolvedMonitoring and Reporting (DBP)
—TTHM
August 31, 2018 – August 30, 2019
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
September 1, 2014 – August 31, 2015
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Diquat | — | Resolved |
| August 31, 2018 – August 30, 2019 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| September 1, 2014 – August 31, 2015 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- October 29, 2025State Compliance achieved1 linked violation
- September 25, 2025State Compliance achieved1 linked violation
- January 23, 2025State Compliance achieved2 linked violations
- January 23, 2025State Public Notification requested2 linked violations
- January 15, 2025State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 15, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- November 7, 2024State Public Notification requested1 linked violation
- November 7, 2024State Violation/Reminder Notice1 linked violation
- August 7, 2024State Violation/Reminder Notice1 linked violation
- August 7, 2024State Public Notification requested1 linked violation
- November 7, 2023State Compliance achieved7 linked violations
- October 18, 2023State Compliance achieved2 linked violations
- October 18, 2023State Public Notification requested2 linked violations
- October 18, 2023State Violation/Reminder Notice2 linked violations
- June 21, 2023State Public Notification requested7 linked violations
- June 21, 2023State Violation/Reminder Notice7 linked violations
- December 22, 2022State Compliance achieved1 linked violation
- September 29, 2022State Compliance achieved1 linked violation
- February 2, 2022State Violation/Reminder Notice1 linked violation
- February 2, 2022State Public Notification requested1 linked violation
- January 4, 2022State Violation/Reminder Notice1 linked violation
- October 20, 2021State Violation/Reminder Notice2 linked violations
- October 20, 2021State Public Notification requested2 linked violations
- August 30, 2021State Compliance achieved2 linked violations
- August 30, 2021State Compliance achieved2 linked violations
- August 30, 2021State Compliance achieved2 linked violations
- October 19, 2020State Violation/Reminder Notice2 linked violations
- October 19, 2020State Public Notification requested2 linked violations
- January 22, 2020State Violation/Reminder Notice1 linked violation
- January 22, 2020State Public Notification requested1 linked violation
- October 18, 2019State Public Notification requested2 linked violations
- October 18, 2019State Violation/Reminder Notice2 linked violations
- August 24, 2017State Compliance achieved2 linked violations
- July 20, 2017State Compliance achieved1 linked violation
- July 18, 2017State Public Notification requested1 linked violation
- July 18, 2017State Violation/Reminder Notice1 linked violation
- September 30, 2016State Compliance achieved1 linked violation
- July 15, 2016State Public Notification requested1 linked violation
- July 15, 2016State Violation/Reminder Notice1 linked violation
- October 19, 2015State Public Notification requested2 linked violations
- October 19, 2015State Violation/Reminder Notice2 linked violations
- July 16, 2015State Compliance achieved1 linked violation
- July 15, 2015State Violation/Reminder Notice1 linked violation
- January 24, 2014State Public Notification requested1 linked violation
- January 24, 2014State Violation/Reminder Notice1 linked violation
- July 30, 2012State Compliance achieved1 linked violation
- July 12, 2012State Public Notification requested1 linked violation
- July 12, 2012State Violation/Reminder Notice1 linked violation
- September 24, 2010State Compliance achieved1 linked violation
- August 7, 2010State Violation/Reminder Notice1 linked violation
- August 7, 2010State Public Notification requested1 linked violation
- May 7, 2010State Compliance achieved2 linked violations
- May 15, 2009State Compliance achieved1 linked violation
- July 18, 2008State Public Notification received3 linked violations
- June 25, 2008State Violation/Reminder Notice3 linked violations
- February 2, 2007State Compliance achieved4 linked violations
- January 14, 2007State Violation/Reminder Notice3 linked violations
- January 14, 2007State Violation/Reminder Notice3 linked violations
- January 14, 2007State Public Notification requested4 linked violations
- January 14, 2007State Public Notification requested3 linked violations
- October 5, 2005State Compliance achieved15 linked violations
- September 27, 2005State Violation/Reminder Notice2 linked violations
- September 27, 2005State Violation/Reminder Notice1 linked violation
- January 4, 2005State Public Notification requested6 linked violations
- January 3, 2005State Violation/Reminder Notice1 linked violation
- January 3, 2005State Violation/Reminder Notice3 linked violations
- January 3, 2005State Public Notification requested8 linked violations
- January 3, 2005State Violation/Reminder Notice2 linked violations
- January 3, 2005State Violation/Reminder Notice1 linked violation
- January 3, 2005State Public Notification requested4 linked violations
- January 3, 2005State Violation/Reminder Notice4 linked violations
- January 3, 2005State Public Notification requested3 linked violations
- January 3, 2005State Public Notification requested5 linked violations
- January 3, 2005State Public Notification requested5 linked violations
- January 3, 2005State Violation/Reminder Notice6 linked violations
- October 29, 2004State Violation/Reminder Notice2 linked violations
- October 29, 2004State Violation/Reminder Notice2 linked violations
- January 30, 2004State Public Notification received1 linked violation
- September 22, 2003State Violation/Reminder Notice2 linked violations
- September 22, 2003State Compliance achieved1 linked violation
- September 22, 2003State Violation/Reminder Notice1 linked violation
- September 22, 2003State Public Notification requested1 linked violation
- August 15, 2003State Violation/Reminder Notice2 linked violations
- August 15, 2003State Compliance achieved1 linked violation
- April 3, 2003State Public Notification received1 linked violation
- November 18, 2002State Compliance achieved2 linked violations
- January 30, 2001State Compliance achieved2 linked violations
Common questions
Is RIVER ROCK COUNTY WATER AND SEWER DIST required to publish a Consumer Confidence Report?
- Yes. RIVER ROCK COUNTY WATER AND SEWER DIST 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 ROCK COUNTY WATER AND SEWER DIST’s next Consumer Confidence Report due?
- RIVER ROCK COUNTY WATER AND SEWER DIST’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does RIVER ROCK COUNTY WATER AND SEWER DIST have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for RIVER ROCK COUNTY WATER AND SEWER DIST.
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
CLARKSON, CHRISTINE
406-581-7644
BELGRADE, MT 59714