RENO, NV · Churchill County
SAGE VALLEY MHP LLC Water System
Consumer Confidence Report status
SAGE VALLEY MHP LLC 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 SAGE VALLEY MHP LLC.
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 Nevada’s official records. Always confirm current status with Nevada before making decisions based on this information.
System facts
- System ID (PWSID)
- NV0002023
- System type
- Community Water System
- Population served
- 188
- Service connections
- 45
- Ownership
- privately owned
- Water source
- groundwater (wells)
SAGE VALLEY MHP LLC is one of 293 community water systems in Nevada in the 500 or fewer people size category, serving 188 people from groundwater.
As of August 1, 2026, its federal record holds 13 entries between 2011 and 2021, all of which EPA lists as closed. Nothing has been added since 2021.
All 13 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 volatile organic chemicals, the Stage 1 Disinfectants and Disinfection Byproducts Rule, and the Total Coliform Rules.
Violation history
Monitoring, Routine (RTCR)
—Revised Total Coliform Rule
May 1, 2021 – May 31, 2021
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2016 – December 31, 2016
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2016 – June 30, 2016
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2014 – December 31, 2014
ResolvedMonitoring, Regular
—1,1,1-Trichloroethane
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—CHLOROBENZENE
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—Toluene
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—Styrene
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—1,2-Dichloropropane
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—Trichloroethylene
January 1, 2014 – December 31, 2016
ResolvedMonitoring and Reporting (DBP)
—TTHM
January 1, 2013 – December 31, 2013
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
January 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Arsenic
October 1, 2011 – December 31, 2011
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| May 1, 2021 – May 31, 2021 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| October 1, 2016 – December 31, 2016 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2016 – June 30, 2016 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2014 – December 31, 2014 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | 1,1,1-Trichloroethane | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | CHLOROBENZENE | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | Toluene | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | Styrene | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | 1,2-Dichloropropane | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | Trichloroethylene | — | Resolved |
| January 1, 2013 – December 31, 2013 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| January 1, 2012 – December 31, 2012 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Arsenic | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- November 3, 2021State Compliance achieved3 linked violations
- September 17, 2021State Public Notification requested2 linked violations
- August 27, 2021State Compliance achieved3 linked violations
- August 5, 2021State Compliance achieved4 linked violations
- July 1, 2021State Public Notification received5 linked violations
- June 16, 2021State Public Notification requested3 linked violations
- January 8, 2021State Compliance achieved2 linked violations
- November 25, 2020State Violation/Reminder Notice2 linked violations
- November 16, 2020State Public Notification requested2 linked violations
- May 28, 2020State Violation/Reminder Notice2 linked violations
- May 28, 2020State Public Notification requested2 linked violations
- May 5, 2020State Public Notification requested2 linked violations
- March 23, 2020State Public Notification requested2 linked violations
- January 22, 2020State Compliance achieved3 linked violations
- November 15, 2019State Violation/Reminder Notice2 linked violations
- August 21, 2019State Compliance achieved4 linked violations
- August 21, 2019State Compliance achieved2 linked violations
- August 20, 2019State Violation/Reminder Notice2 linked violations
- August 20, 2019State Public Notification requested2 linked violations
- August 20, 2019State Violation/Reminder Notice2 linked violations
- April 15, 2019State Public Notification requested2 linked violations
- February 7, 2019State Violation/Reminder Notice3 linked violations
- February 7, 2019State Public Notification requested3 linked violations
- January 2, 2019State Violation/Reminder Notice2 linked violations
- November 5, 2018State Public Notification requested3 linked violations
- November 5, 2018State Violation/Reminder Notice3 linked violations
- October 1, 2018State Violation/Reminder Notice2 linked violations
- August 29, 2017State Compliance achieved22 linked violations
- July 13, 2017State Public Notification received32 linked violations
- April 26, 2017State Compliance achieved6 linked violations
- April 19, 2017State Violation/Reminder Notice5 linked violations
- April 19, 2017State Violation/Reminder Notice25 linked violations
- April 19, 2017State Public Notification requested24 linked violations
- January 25, 2017State Public Notification requested2 linked violations
- August 26, 2016State Compliance achieved16 linked violations
- July 1, 2016State Public Notification requested2 linked violations
- July 1, 2016State Public Notification requested2 linked violations
- June 30, 2016State Compliance achieved3 linked violations
- January 28, 2016State Violation/Reminder Notice2 linked violations
- January 27, 2016State Violation/Reminder Notice3 linked violations
- January 27, 2016State Public Notification requested3 linked violations
- September 9, 2015State Compliance achieved3 linked violations
- August 6, 2015State Violation/Reminder Notice3 linked violations
- April 28, 2015State Public Notification requested4 linked violations
- April 28, 2015State Public Notification requested2 linked violations
- April 28, 2015State Violation/Reminder Notice2 linked violations
- April 28, 2015State Public Notification requested4 linked violations
- May 8, 2014State Violation/Reminder Notice4 linked violations
- May 8, 2014State Public Notification requested4 linked violations
- June 30, 2013State Compliance achieved11 linked violations
- May 14, 2013State Violation/Reminder Notice5 linked violations
- February 14, 2013State Violation/Reminder Notice3 linked violations
- December 19, 2012State Violation/Reminder Notice2 linked violations
- December 19, 2012State Public Notification requested4 linked violations
- April 23, 2012State Violation/Reminder Notice4 linked violations
- April 23, 2012State Public Notification requested3 linked violations
- February 2, 2010State Public Notification requested4 linked violations
- February 9, 2009State Compliance achieved5 linked violations
- February 9, 2009State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- September 13, 2007State Compliance achieved9 linked violations
- April 24, 2007State Public Notification requested6 linked violations
- April 24, 2007State Violation/Reminder Notice6 linked violations
- January 24, 2007State Formal Notice of Violation issued6 linked violations
- October 20, 2006State Public Notification requested3 linked violations
- September 28, 2004State Public Notification requested1 linked violation
- October 1, 2002State Public Notification requested6 linked violations
Common questions
Is SAGE VALLEY MHP LLC required to publish a Consumer Confidence Report?
- Yes. SAGE VALLEY MHP LLC 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 SAGE VALLEY MHP LLC’s next Consumer Confidence Report due?
- SAGE VALLEY MHP LLC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does SAGE VALLEY MHP LLC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for SAGE VALLEY MHP LLC.
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
JENNINGS, JOEY
775-453-2160
RENO, NV 89509