Lake Lillian, MN · Kandiyohi County
Lake Lillian Water System
Consumer Confidence Report status
Lake Lillian 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 Lake Lillian.
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)
- MN1340004
- System type
- Community Water System
- Population served
- 236
- Service connections
- 136
- Ownership
- local government
- Water source
- groundwater (wells)
Lake Lillian is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 236 people from groundwater.
As of August 1, 2026, its federal record holds 19 entries between 2019 and 2026, all of which EPA lists as closed.
None of the 19 are monitoring or reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset; these involve water-quality, treatment, or public-notice findings instead. The record involves inorganic chemicals and the Public Notice Rule and Revised PN Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2026 – March 31, 2026
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
September 9, 2025 – December 2, 2025
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2025 – June 30, 2025
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
January 22, 2025 – February 27, 2025
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2025 – March 31, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2024 – December 31, 2024
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
September 22, 2024 – February 27, 2025
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2024 – September 30, 2024
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2024 – June 30, 2024
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2024 – March 31, 2024
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2023 – December 31, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2023 – September 30, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2023 – June 30, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2022 – December 31, 2022
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2020 – December 31, 2020
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2020 – March 31, 2020
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2019 – December 31, 2019
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2019 – September 30, 2019
ArchivedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2019 – June 30, 2019
Archived
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2026 – March 31, 2026 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| September 9, 2025 – December 2, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| April 1, 2025 – June 30, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| January 22, 2025 – February 27, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2025 – March 31, 2025 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2024 – December 31, 2024 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| September 22, 2024 – February 27, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2024 – September 30, 2024 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| April 1, 2024 – June 30, 2024 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| January 1, 2024 – March 31, 2024 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2023 – December 31, 2023 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| July 1, 2023 – September 30, 2023 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| April 1, 2023 – June 30, 2023 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2022 – December 31, 2022 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2020 – December 31, 2020 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| January 1, 2020 – March 31, 2020 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| October 1, 2019 – December 31, 2019 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| July 1, 2019 – September 30, 2019 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
| April 1, 2019 – June 30, 2019 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Archived |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- April 3, 2026State Public Notification requested1 linked violation
- April 3, 2026State Compliance Meeting conducted1 linked violation
- April 3, 2026State Formal Notice of Violation issued1 linked violation
- March 30, 2026State Public Notification received1 linked violation
- December 2, 2025State Public Notification received1 linked violation
- December 2, 2025State Compliance achieved1 linked violation
- October 28, 2025State Formal Notice of Violation issued1 linked violation
- October 28, 2025State Public Notification requested1 linked violation
- October 28, 2025State Compliance Meeting conducted1 linked violation
- October 17, 2025State Formal Notice of Violation issued1 linked violation
- July 31, 2025State Formal Notice of Violation issued1 linked violation
- July 31, 2025State Public Notification requested1 linked violation
- July 31, 2025State Compliance Meeting conducted1 linked violation
- June 30, 2025State Public Notification received1 linked violation
- May 6, 2025State Compliance Meeting conducted1 linked violation
- May 6, 2025State Public Notification requested1 linked violation
- May 6, 2025State Formal Notice of Violation issued1 linked violation
- February 27, 2025State Compliance achieved1 linked violation
- February 27, 2025State Compliance achieved1 linked violation
- February 27, 2025State Public Notification received1 linked violation
- February 25, 2025State Formal Notice of Violation issued1 linked violation
- February 25, 2025State Public Notification requested1 linked violation
- February 25, 2025State Compliance Meeting conducted1 linked violation
- January 16, 2025State Formal Notice of Violation issued1 linked violation
- December 13, 2024State Formal Notice of Violation issued1 linked violation
- December 13, 2024State Public Notification requested1 linked violation
- December 13, 2024State Compliance Meeting conducted1 linked violation
- October 22, 2024State Formal Notice of Violation issued1 linked violation
- August 13, 2024State Compliance Meeting conducted1 linked violation
- August 13, 2024State Public Notification requested1 linked violation
- August 13, 2024State Formal Notice of Violation issued1 linked violation
- May 7, 2024State Compliance achieved1 linked violation
- May 7, 2024State Public Notification received1 linked violation
- April 26, 2024State Compliance Meeting conducted1 linked violation
- April 26, 2024State Formal Notice of Violation issued1 linked violation
- April 26, 2024State Public Notification requested1 linked violation
- April 25, 2024State Formal Notice of Violation issued1 linked violation
- January 31, 2024State Compliance Meeting conducted1 linked violation
- January 31, 2024State Public Notification requested1 linked violation
- January 31, 2024State Formal Notice of Violation issued1 linked violation
- December 21, 2023State Compliance Meeting conducted1 linked violation
- December 21, 2023State Formal Notice of Violation issued1 linked violation
- December 21, 2023State Public Notification requested1 linked violation
- September 20, 2023State Public Notification requested1 linked violation
- September 20, 2023State Compliance Meeting conducted1 linked violation
- September 20, 2023State Formal Notice of Violation issued1 linked violation
- May 16, 2023State Public Notification received1 linked violation
- May 15, 2023State Compliance Meeting conducted1 linked violation
- May 15, 2023State Formal Notice of Violation issued1 linked violation
- May 15, 2023State Public Notification requested1 linked violation
- November 16, 2022State Public Notification received1 linked violation
- November 10, 2022State Compliance Meeting conducted1 linked violation
- November 10, 2022State Violation/Reminder Notice1 linked violation
- November 10, 2022State Public Notification requested1 linked violation
- August 10, 2021State Compliance achieved1 linked violation
- June 16, 2021State Violation/Reminder Notice1 linked violation
- April 8, 2021State Compliance Meeting conducted1 linked violation
- April 8, 2021State Violation/Reminder Notice1 linked violation
- March 18, 2021State Public Notification received3 linked violations
- February 24, 2021State Public Notification requested1 linked violation
- February 24, 2021State Violation/Reminder Notice2 linked violations
- February 24, 2021State Compliance Meeting conducted1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued3 linked violations
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- January 29, 2021State Administrative/Compliance Order without penalty issued1 linked violation
- November 20, 2020State Violation/Reminder Notice1 linked violation
- November 20, 2020State Compliance Meeting conducted1 linked violation
- November 20, 2020State Public Notification requested1 linked violation
- June 4, 2020State Public Notification requested2 linked violations
- June 4, 2020State Compliance Meeting conducted2 linked violations
- June 4, 2020State Violation/Reminder Notice2 linked violations
- December 30, 2019State Public Notification received1 linked violation
- December 9, 2019State Compliance Meeting conducted7 linked violations
- December 9, 2019State Public Notification requested1 linked violation
- August 9, 2019State Public Notification requested1 linked violation
- August 9, 2019State Compliance Meeting conducted1 linked violation
- August 9, 2019State Violation/Reminder Notice1 linked violation
- July 23, 2019State Administrative/Compliance Order without penalty issued1 linked violation
- July 23, 2019State Administrative/Compliance Order without penalty issued7 linked violations
- June 25, 2019State Compliance Meeting conducted4 linked violations
- June 25, 2019State Public Notification requested1 linked violation
- June 25, 2019State Formal Notice of Violation issued1 linked violation
- January 9, 2019State Formal Notice of Violation issued1 linked violation
- January 9, 2019State Public Notification requested1 linked violation
- January 9, 2019State Compliance Meeting conducted1 linked violation
- January 12, 2010State Compliance achieved1 linked violation
- September 14, 2009State Violation/Reminder Notice1 linked violation
- June 12, 2009State Violation/Reminder Notice1 linked violation
- May 11, 2009State Public Notification received3 linked violations
- April 14, 2009State Violation/Reminder Notice1 linked violation
- March 3, 2009State Bilateral Compliance Agreement signed1 linked violation
- February 9, 2009State Public Notification received1 linked violation
- January 13, 2009State Formal Notice of Violation issued6 linked violations
- March 24, 2008State Compliance achieved1 linked violation
- December 18, 2006State Bilateral Compliance Agreement signed1 linked violation
- December 8, 2006State Public Notification received1 linked violation
- November 17, 2006State Compliance Meeting conducted1 linked violation
- September 30, 1984State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 1984State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- September 30, 1984State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 30, 1982State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
Common questions
Is Lake Lillian required to publish a Consumer Confidence Report?
- Yes. Lake Lillian 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 Lake Lillian’s next Consumer Confidence Report due?
- Lake Lillian’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Lake Lillian have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for Lake Lillian.
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
Lake Lillian City Council
3209051737
Lake Lillian, MN 56253