FIELDING, UT · Box Elder County
RIVERSIDE-NORTH GARLAND WATER CO Water System
Consumer Confidence Report status
RIVERSIDE-NORTH GARLAND WATER CO 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 1 item for RIVERSIDE-NORTH GARLAND WATER CO that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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 Utah’s official records. Always confirm current status with Utah before making decisions based on this information.
System facts
- System ID (PWSID)
- UTAH02015
- System type
- Community Water System
- Population served
- 1,193
- Service connections
- 457
- Ownership
- privately owned
- Water source
- groundwater (wells)
RIVERSIDE-NORTH GARLAND WATER CO is one of 141 community water systems in Utah in the 501 to 3,300 people size category, serving 1,193 people from groundwater.
As of August 1, 2026, its federal record holds 22 entries between 1979 and 2024, of which 1 remains open; none are health-based.
Of the 22, 19 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 inorganic chemicals, the Total Coliform Rules, and the Radionuclides and Revised Rad Rule.
Violation history
Monitoring, Source Water (GWR)
—E. COLI
September 6, 2024
UnaddressedMonitoring, Regular
—Nitrate
January 1, 2020 – December 31, 2020
ResolvedMonitoring, Regular
—Nitrate
January 1, 2020 – December 31, 2020
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
August 1, 2017 – August 31, 2017
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
July 1, 2011 – July 31, 2011
ArchivedMonitoring, Regular
—Nitrate
January 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Thallium, Total
January 1, 2008 – December 31, 2010
ResolvedMonitoring, Regular
—Mercury
January 1, 2008 – December 31, 2010
ResolvedMonitoring, Regular
—Antimony, Total
January 1, 2008 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2002 – December 31, 2007
ResolvedMonitoring, Regular
—Radium-226
January 1, 2002 – December 31, 2007
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2002 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
October 1, 1994 – October 31, 1994
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 1994 – August 31, 1994
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
October 1, 1993 – October 31, 1993
ArchivedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
October 1, 1991 – October 31, 1991
ArchivedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
September 1, 1991 – September 30, 1991
ResolvedMonitoring, Regular
—Nitrate
June 24, 1979 – July 23, 1979
ArchivedMonitoring, Regular
—Cadmium
June 24, 1979 – July 23, 1979
ArchivedMonitoring, Regular
—Mercury
June 24, 1979 – July 23, 1979
ArchivedMonitoring, Regular
—Fluoride
June 24, 1979 – July 23, 1979
ArchivedMonitoring, Regular
—Chromium
June 24, 1979 – July 23, 1979
Archived
Unaddressed no corrective action on record yetResolved 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 |
|---|---|---|---|---|
| September 6, 2024 | Monitoring, Source Water (GWR) | E. COLI | — | Unaddressed |
| January 1, 2020 – December 31, 2020 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2020 – December 31, 2020 | Monitoring, Regular | Nitrate | — | Resolved |
| August 1, 2017 – August 31, 2017 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| July 1, 2011 – July 31, 2011 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Archived |
| January 1, 2010 – December 31, 2010 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Thallium, Total | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Mercury | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Antimony, Total | — | Resolved |
| January 1, 2002 – December 31, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2002 – December 31, 2007 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2002 – December 31, 2007 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 1994 – October 31, 1994 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| August 1, 1994 – August 31, 1994 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| October 1, 1993 – October 31, 1993 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| October 1, 1991 – October 31, 1991 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| September 1, 1991 – September 30, 1991 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
| June 24, 1979 – July 23, 1979 | Monitoring, Regular | Nitrate | — | Archived |
| June 24, 1979 – July 23, 1979 | Monitoring, Regular | Cadmium | — | Archived |
| June 24, 1979 – July 23, 1979 | Monitoring, Regular | Mercury | — | Archived |
| June 24, 1979 – July 23, 1979 | Monitoring, Regular | Fluoride | — | Archived |
| June 24, 1979 – July 23, 1979 | Monitoring, Regular | Chromium | — | Archived |
Unaddressed no corrective action on record yetResolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- November 13, 2025State Public Notification requested1 linked violation
- November 13, 2025State Formal Notice of Violation issued1 linked violation
- August 26, 2025State Compliance achieved2 linked violations
- August 12, 2025State Compliance achieved1 linked violation
- November 23, 2024State Public Notification requested1 linked violation
- November 23, 2024State Formal Notice of Violation issued1 linked violation
- November 7, 2024State Formal Notice of Violation issued2 linked violations
- November 7, 2024State Public Notification requested2 linked violations
- December 9, 2021State Compliance achieved2 linked violations
- October 19, 2021State Compliance achieved1 linked violation
- February 7, 2021State Formal Notice of Violation issued2 linked violations
- February 7, 2021State Public Notification requested2 linked violations
- February 6, 2021State Public Notification requested1 linked violation
- February 6, 2021State Formal Notice of Violation issued1 linked violation
- February 6, 2021State Public Notification requested1 linked violation
- February 6, 2021State Formal Notice of Violation issued1 linked violation
- January 31, 2020State Public Notification requested1 linked violation
- January 31, 2020State Formal Notice of Violation issued1 linked violation
- June 15, 2018State Public Notification requested2 linked violations
- June 15, 2018State Formal Notice of Violation issued1 linked violation
- September 22, 2017State Compliance achieved1 linked violation
- September 20, 2017State Compliance achieved2 linked violations
- September 15, 2017State Formal Notice of Violation issued2 linked violations
- August 23, 2017State Compliance achieved2 linked violations
- August 23, 2017State Compliance achieved2 linked violations
- August 17, 2017State Public Notification requested1 linked violation
- July 24, 2017State Public Notification requested1 linked violation
- July 24, 2017State Formal Notice of Violation issued1 linked violation
- July 24, 2017State Public Notification requested1 linked violation
- July 22, 2017State Public Notification requested2 linked violations
- July 14, 2017State Public Notification requested2 linked violations
- June 6, 2017State Compliance achieved1 linked violation
- May 14, 2017State Public Notification requested2 linked violations
- October 6, 2015State Compliance achieved1 linked violation
- April 6, 2015State Compliance achieved2 linked violations
- January 16, 2015State Public Notification requested3 linked violations
- January 16, 2015State Public Notification requested3 linked violations
- September 18, 2011State Public Notification requested3 linked violations
- February 11, 2011State Compliance achieved2 linked violations
- January 17, 2011State Public Notification requested15 linked violations
- January 15, 2011State Formal Notice of Violation issued2 linked violations
- January 15, 2011State Public Notification requested3 linked violations
- January 29, 2010State Formal Notice of Violation issued5 linked violations
- January 29, 2010State Compliance achieved2 linked violations
- December 2, 1993State Formal Notice of Violation issued4 linked violations
- November 5, 1992Federal Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 20, 1992Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- March 14, 1991State Technical Assistance Visit2 linked violations
- October 1, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 1, 1990State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- September 4, 1990State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- September 4, 1990State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
- May 30, 1990State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
- April 6, 1990State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
- December 6, 1989State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
- October 10, 1989State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
Common questions
Is RIVERSIDE-NORTH GARLAND WATER CO required to publish a Consumer Confidence Report?
- Yes. RIVERSIDE-NORTH GARLAND WATER CO 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 RIVERSIDE-NORTH GARLAND WATER CO’s next Consumer Confidence Report due?
- RIVERSIDE-NORTH GARLAND WATER CO’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does RIVERSIDE-NORTH GARLAND WATER CO have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for RIVERSIDE-NORTH GARLAND WATER CO that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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
CHRISTOFFERSEN, CRAIG E
435-279-0245
FIELDING, UT 84311