Ellsworth, MN · Nobles County
Ellsworth Water System
Consumer Confidence Report status
Ellsworth 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 Ellsworth.
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 Minnesota’s official records. Always confirm current status with Minnesota before making decisions based on this information.
System facts
- System ID (PWSID)
- MN1530005
- System type
- Community Water System
- Population served
- 462
- Service connections
- 253
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
Ellsworth is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 462 people from surface water.
As of August 1, 2026, its federal record holds 7 entries between 2014 and 2024, all of which EPA lists as closed.
Of the 7, 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 inorganic chemicals, the Lead and Copper Rule, and the Stage 2 Disinfectants and Disinfection Byproducts Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedNitrate
October 1, 2024 – December 31, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
July 1, 2024 – September 30, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
July 1, 2023 – September 30, 2023
ResolvedWater Quality Parameter M/R
—Lead and Copper Rule
July 1, 2019 – December 31, 2019
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
April 1, 2019 – June 30, 2019
ResolvedLead Consumer Notice
—Lead and Copper Rule
January 1, 2017 – June 22, 2017
ResolvedMonitoring and Reporting (DBP)
—TTHM
January 1, 2014 – November 2, 2016
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2024 – December 31, 2024 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| July 1, 2024 – September 30, 2024 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| July 1, 2023 – September 30, 2023 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| July 1, 2019 – December 31, 2019 | Water Quality Parameter M/R | Lead and Copper Rule | — | Resolved |
| April 1, 2019 – June 30, 2019 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| January 1, 2017 – June 22, 2017 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| January 1, 2014 – November 2, 2016 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- April 15, 2025State Compliance achieved1 linked violation
- April 15, 2025State Compliance achieved1 linked violation
- October 16, 2024State Public Notification received1 linked violation
- October 10, 2024State Formal Notice of Violation issued1 linked violation
- October 10, 2024State Public Notification requested1 linked violation
- October 10, 2024State Compliance Meeting conducted1 linked violation
- August 14, 2024State Public Notification received1 linked violation
- August 9, 2024State Public Notification requested1 linked violation
- August 9, 2024State Formal Notice of Violation issued1 linked violation
- August 9, 2024State Compliance Meeting conducted1 linked violation
- February 13, 2024State Compliance achieved1 linked violation
- August 2, 2023State Public Notification received1 linked violation
- July 27, 2023State Formal Notice of Violation issued1 linked violation
- July 27, 2023State Compliance Meeting conducted1 linked violation
- July 27, 2023State Public Notification requested1 linked violation
- January 16, 2020State Public Notification requested3 linked violations
- January 16, 2020State Formal Notice of Violation issued3 linked violations
- June 4, 2019State Public Notification received1 linked violation
- May 3, 2019State Compliance Meeting conducted3 linked violations
- June 22, 2017State Compliance achieved1 linked violation
- April 6, 2017State Formal Notice of Violation issued2 linked violations
- February 24, 2017State Violation/Reminder Notice1 linked violation
- December 27, 2016State Violation/Reminder Notice2 linked violations
- December 9, 2016State Public Notification requested2 linked violations
- December 9, 2016State Formal Notice of Violation issued2 linked violations
- November 2, 2016State Compliance achieved2 linked violations
- October 20, 2016State Violation/Reminder Notice2 linked violations
- September 13, 2016State Violation/Reminder Notice2 linked violations
- August 23, 2000State Public Notification received1 linked violation
- August 23, 2000State Compliance achieved1 linked violation
- August 16, 2000State Compliance Meeting conducted1 linked violation
- August 16, 2000State Technical Assistance Visit1 linked violation
- August 16, 2000State Formal Notice of Violation issued1 linked violation
- August 16, 2000State Public Notification requested1 linked violation
- September 1, 1994State Compliance achieved1 linked violation
- July 15, 1992State Site Visit for enforcement purposes1 linked violation
- July 15, 1992State Violation/Reminder Notice1 linked violation
- July 15, 1992State Technical Assistance Visit1 linked violation
- September 30, 1987State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 30, 1987State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
- September 30, 1986State Public Notification requested1 linked violation
- September 30, 1986State Violation/Reminder Notice1 linked violation
Common questions
Is Ellsworth required to publish a Consumer Confidence Report?
- Yes. Ellsworth 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 Ellsworth’s next Consumer Confidence Report due?
- Ellsworth’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Ellsworth have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for Ellsworth.
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
Ellsworth City Council
5079672373
Ellsworth, MN 56129-1092