Is LYMAN, VILLAGE OF required to publish a Consumer Confidence Report?

Yes. LYMAN, VILLAGE OF 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 LYMAN, VILLAGE OF’s next Consumer Confidence Report due?

LYMAN, VILLAGE OF’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.

LYMAN, NE · Scotts Bluff County

LYMAN, VILLAGE OF Water System

Consumer Confidence Report status

LYMAN, VILLAGE OF 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 LYMAN, VILLAGE OF.

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 Nebraska’s official records. Always confirm current status with Nebraska before making decisions based on this information.

System facts

System ID (PWSID): NE3115710
System type: Community Water System
Population served: 325
Service connections: 198
Ownership: local government
Water source: groundwater (wells)

LYMAN, VILLAGE OF is one of 568 community water systems in Nebraska in the 500 or fewer people size category, serving 325 people from groundwater.

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

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

Violation history

Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
October 1, 2012 – October 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
July 1, 2012 – September 30, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
April 1, 2012 – June 30, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
January 1, 2012 – March 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
July 1, 2011 – September 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
April 1, 2011 – June 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
January 1, 2011 – March 31, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
October 1, 2010 – December 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
July 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
April 1, 2010 – June 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
October 1, 2009 – December 31, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
April 1, 2009 – June 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
October 1, 2007 – December 31, 2007
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
February 1, 2007 – February 28, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
October 1, 2006 – December 31, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
July 1, 2005 – September 30, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
April 1, 2005 – June 30, 2005
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
November 1, 2002 – November 30, 2002
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
October 1, 2012 – October 31, 2012	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved
July 1, 2012 – September 30, 2012	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
April 1, 2012 – June 30, 2012	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
January 1, 2012 – March 31, 2012	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
July 1, 2011 – September 30, 2011	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
April 1, 2011 – June 30, 2011	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
January 1, 2011 – March 31, 2011	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
October 1, 2010 – December 31, 2010	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
July 1, 2010 – September 30, 2010	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
April 1, 2010 – June 30, 2010	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
January 1, 2010 – March 31, 2010	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
October 1, 2009 – December 31, 2009	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
April 1, 2009 – June 30, 2009	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
October 1, 2007 – December 31, 2007	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
February 1, 2007 – February 28, 2007	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved
October 1, 2006 – December 31, 2006	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
July 1, 2005 – September 30, 2005	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
April 1, 2005 – June 30, 2005	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
November 1, 2002 – November 30, 2002	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

October 31, 2013State Compliance achieved1 linked violation
August 19, 2013State Compliance achieved31 linked violations
March 26, 2013State Compliance achievedgeneral compliance action — not tied to a specific violation on record
November 2, 2012State Public Notification received1 linked violation
October 25, 2012State Public Notification received1 linked violation
October 18, 2012State Public Notification requested1 linked violation
October 18, 2012State Violation/Reminder Notice1 linked violation
October 2, 2012State Violation/Reminder Notice1 linked violation
October 2, 2012State Public Notification requested1 linked violation
July 30, 2012State Public Notification received1 linked violation
July 16, 2012State Violation/Reminder Notice1 linked violation
July 16, 2012State Public Notification requested1 linked violation
May 31, 2012State Public Notification received1 linked violation
April 30, 2012State Violation/Reminder Notice1 linked violation
April 30, 2012State Public Notification requested1 linked violation
October 5, 2011State Public Notification received1 linked violation
October 3, 2011State Violation/Reminder Notice1 linked violation
October 3, 2011State Public Notification requested1 linked violation
August 1, 2011State Public Notification received1 linked violation
July 20, 2011State Violation/Reminder Notice1 linked violation
July 20, 2011State Public Notification requested1 linked violation
May 2, 2011State Public Notification received1 linked violation
April 13, 2011State Violation/Reminder Notice1 linked violation
April 13, 2011State Public Notification requested1 linked violation
February 10, 2011State Public Notification received1 linked violation
January 18, 2011State Violation/Reminder Notice1 linked violation
January 18, 2011State Public Notification requested1 linked violation
November 1, 2010State Public Notification received1 linked violation
October 25, 2010State Public Notification requested1 linked violation
October 25, 2010State Violation/Reminder Notice1 linked violation
July 29, 2010State Public Notification received1 linked violation
July 14, 2010State Violation/Reminder Notice1 linked violation
July 14, 2010State Public Notification requested1 linked violation
May 4, 2010State Public Notification received1 linked violation
April 27, 2010State Violation/Reminder Notice1 linked violation
April 27, 2010State Public Notification requested1 linked violation
January 29, 2010State Public Notification received1 linked violation
January 19, 2010State Violation/Reminder Notice1 linked violation
January 19, 2010State Public Notification requested1 linked violation
November 4, 2009State Public Notification received1 linked violation
October 19, 2009State Violation/Reminder Notice1 linked violation
October 19, 2009State Public Notification requested1 linked violation
August 31, 2009State Compliance achieved1 linked violation
July 6, 2009State Public Notification received1 linked violation
June 24, 2009State Public Notification requested1 linked violation
June 24, 2009State Violation/Reminder Notice1 linked violation
April 1, 2009State Public Notification received1 linked violation
March 10, 2009State Violation/Reminder Notice1 linked violation
March 10, 2009State Public Notification requested1 linked violation
February 11, 2009State Public Notification received1 linked violation
January 29, 2009State Violation/Reminder Notice1 linked violation
January 29, 2009State Public Notification requested1 linked violation
November 24, 2008State Violation/Reminder Notice1 linked violation
November 24, 2008State Public Notification requested1 linked violation
October 30, 2008State Compliance achieved1 linked violation
October 30, 2008State Public Notification received1 linked violation
October 1, 2008State Public Notification received1 linked violation
September 10, 2008State Public Notification requested1 linked violation
September 10, 2008State Violation/Reminder Notice1 linked violation
July 31, 2008State Public Notification received1 linked violation
July 18, 2008State Violation/Reminder Notice1 linked violation
May 2, 2008State Public Notification received1 linked violation
April 10, 2008State Violation/Reminder Notice1 linked violation
April 10, 2008State Public Notification requested1 linked violation
February 28, 2008State Compliance achieved1 linked violation
January 22, 2008State Public Notification received1 linked violation
January 15, 2008State Public Notification requested1 linked violation
January 15, 2008State Violation/Reminder Notice1 linked violation
November 21, 2007State Public Notification received1 linked violation
November 14, 2007State Public Notification requested1 linked violation
November 14, 2007State Violation/Reminder Notice1 linked violation
October 24, 2007State Public Notification requested1 linked violation
October 24, 2007State Violation/Reminder Notice1 linked violation
October 1, 2007State Public Notification received1 linked violation
August 29, 2007State Public Notification requested1 linked violation
August 29, 2007State Violation/Reminder Notice1 linked violation
July 27, 2007State Public Notification received1 linked violation
July 5, 2007State Violation/Reminder Notice1 linked violation
July 5, 2007State Public Notification requested1 linked violation
March 26, 2007State Public Notification received1 linked violation
March 15, 2007State Public Notification requested1 linked violation
March 15, 2007State Violation/Reminder Notice1 linked violation
January 31, 2007State Public Notification received1 linked violation
January 25, 2007State Public Notification requested1 linked violation
January 25, 2007State Violation/Reminder Notice1 linked violation
September 25, 2006State Public Notification received1 linked violation
September 13, 2006State Violation/Reminder Notice1 linked violation
September 13, 2006State Public Notification requested1 linked violation
August 7, 2006State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 21, 2006State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 21, 2006State Variance/Exemption issuedgeneral compliance action — not tied to a specific violation on record
July 7, 2006State Public Notification received1 linked violation
June 23, 2006State Public Notification requested1 linked violation
June 23, 2006State Violation/Reminder Notice1 linked violation
May 10, 2006State Compliance achieved1 linked violation
March 24, 2006State Public Notification requested1 linked violation
March 24, 2006State Public Notification received1 linked violation
March 24, 2006State Violation/Reminder Notice1 linked violation
January 25, 2006State Public Notification received1 linked violation
January 18, 2006State Public Notification requested1 linked violation
January 18, 2006State Violation/Reminder Notice1 linked violation
November 21, 2005State Administrative/Compliance Order without penalty issued31 linked violations
September 8, 2005State Violation/Reminder Notice1 linked violation
September 8, 2005State Public Notification requested1 linked violation
July 8, 2005State Public Notification received1 linked violation
July 5, 2005State Public Notification requested1 linked violation
July 5, 2005State Violation/Reminder Notice1 linked violation
May 3, 2005State Public Notification requested1 linked violation
May 3, 2005State Violation/Reminder Notice1 linked violation
May 2, 2005State Public Notification received1 linked violation
January 31, 2005State Public Notification requested1 linked violation
January 31, 2005State Violation/Reminder Notice1 linked violation
January 27, 2005State Public Notification received1 linked violation
July 30, 2004State Compliance achieved1 linked violation
November 30, 2003State Compliance achieved1 linked violation
July 30, 2003State Public Notification received1 linked violation
July 23, 2003State Public Notification requested1 linked violation
July 23, 2003State Violation/Reminder Notice1 linked violation
May 28, 2003State Violation/Reminder Notice1 linked violation
December 6, 2002State Compliance achieved1 linked violation
December 2, 2002State Public Notification received1 linked violation
November 27, 2002State Violation/Reminder Notice1 linked violation
November 27, 2002State Public Notification requested1 linked violation
July 31, 2001State Compliance achieved1 linked violation
August 7, 2000State Public Notification received1 linked violation
July 25, 2000State Violation/Reminder Notice1 linked violation
July 25, 2000State Public Notification requested1 linked violation
November 30, 1999State Compliance achieved1 linked violation
November 22, 1999State Public Notification received1 linked violation
November 2, 1999State Public Notification requested1 linked violation
November 2, 1999State Violation/Reminder Notice1 linked violation
July 31, 1999State Compliance achieved1 linked violation
August 26, 1998State Public Notification requested1 linked violation

Common questions

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

ROBB, KIM

308-787-1444

LYMAN, NE 69352-0301