Is Lewiston required to publish a Consumer Confidence Report?

Yes. Lewiston 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 Lewiston’s next Consumer Confidence Report due?

Lewiston’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

Lewiston, MN · Winona County

Lewiston Water System

Consumer Confidence Report status

Lewiston 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 Lewiston.

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): MN1850006
System type: Community Water System
Population served: 1,512
Service connections: 604
Ownership: local government
Water source: groundwater (wells)

Lewiston is one of 330 community water systems in Minnesota in the 501 to 3,300 people size category, serving 1,512 people from groundwater.

As of August 1, 2026, its federal record holds 3 entries between 1992 and 2017, all of which EPA lists as closed. Nothing has been added since 2017.

Of the 3, 1 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 Radionuclides and Revised Rad Rule and the Total Coliform Rules.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2017 – September 30, 2017
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 8, 2008 – September 30, 2014
Resolved
Monitoring, Routine Minor (TCR)
—
Coliform (TCR)
July 1, 1992 – July 31, 1992
Archived

Resolved 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
July 1, 2017 – September 30, 2017	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 8, 2008 – September 30, 2014	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 1992 – July 31, 1992	Monitoring, Routine Minor (TCR)	Coliform (TCR)	—	Archived

Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

March 15, 2019State Administrative/Compliance Order without penalty issued2 linked violations
March 15, 2019State Compliance achieved2 linked violations
March 13, 2018State Compliance Meeting conducted2 linked violations
March 13, 2018State Formal Notice of Violation issued2 linked violations
December 15, 2017State Formal Notice of Violation issued1 linked violation
December 15, 2017State Compliance Meeting conducted1 linked violation
December 15, 2017State Public Notification requested1 linked violation
March 11, 2014State Administrative/Compliance Order without penalty issued2 linked violations
November 21, 2012State Administrative/Compliance Order without penalty issued1 linked violation
December 1, 2009State Public Notification received1 linked violation
November 2, 2009State Public Notification requested1 linked violation
January 21, 2009State Compliance Meeting conducted3 linked violations
May 30, 2001State Public Notification received2 linked violations
November 30, 2000State Public Notification received1 linked violation
October 7, 1999State Public Notification received1 linked violation
October 30, 1998State Public Notification requested3 linked violations
January 23, 1997State Formal Notice of Violation issued2 linked violations
May 20, 1996State Formal Notice of Violation issued1 linked violation
May 20, 1996State Public Notification requested1 linked violation
May 20, 1996State Violation/Reminder Notice1 linked violation
April 30, 1996State Violation/Reminder Notice1 linked violation
April 30, 1996State Public Notification requested1 linked violation
April 30, 1996State Formal Notice of Violation issued1 linked violation
March 22, 1996State Violation/Reminder Notice2 linked violations
August 15, 1995State Formal Notice of Violation issued1 linked violation
August 15, 1995State Public Notification requested1 linked violation
August 15, 1995State Violation/Reminder Notice1 linked violation
October 15, 1993State Public Notification requested1 linked violation
October 15, 1993State Formal Notice of Violation issued1 linked violation
October 15, 1993State Violation/Reminder Notice1 linked violation
November 15, 1992State Violation/Reminder Notice1 linked violation
November 15, 1992State Public Notification requested1 linked violation
November 15, 1992State Formal Notice of Violation issued1 linked violation
August 15, 1992State Violation/Reminder Notice1 linked violation
August 15, 1992State Formal Notice of Violation issued1 linked violation
August 15, 1992State Public Notification requested1 linked violation
February 15, 1992State Violation/Reminder Notice1 linked violation
February 15, 1992State Public Notification requested1 linked violation
February 15, 1992State Formal Notice of Violation issued1 linked violation
April 15, 1991State Violation/Reminder Notice1 linked violation
April 15, 1991State Public Notification requested1 linked violation
April 15, 1991State Formal Notice of Violation issued2 linked violations
April 1, 1990State Violation/Reminder Notice21 linked violations
September 30, 1984State Violation/Reminder Notice1 linked violation

Common questions

Is Lewiston required to publish a Consumer Confidence Report?: Yes. Lewiston 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 Lewiston’s next Consumer Confidence Report due?: Lewiston’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Lewiston have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for Lewiston.
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

Lewiston City Council

5075232257

Lewiston, MN 55952-0129