BELLWOOD, NE · Butler County
BELLWOOD, VILLAGE OF Water System
Consumer Confidence Report status
BELLWOOD, 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 BELLWOOD, 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)
- NE3102306
- System type
- Community Water System
- Population served
- 435
- Service connections
- 182
- Ownership
- local government
- Water source
- groundwater (wells)
BELLWOOD, VILLAGE OF is one of 568 community water systems in Nebraska in the 500 or fewer people size category, serving 435 people from groundwater.
As of August 1, 2026, its federal record holds 26 entries between 2004 and 2025, all of which EPA lists as closed.
Of the 26, 2 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
Consumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2025 – October 16, 2025
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
May 1, 2015 – May 31, 2015
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
February 1, 2015 – February 28, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2015 – March 31, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2014 – December 31, 2014
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 2014 – September 30, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2014 – September 30, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2014 – March 31, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2013 – December 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2013 – September 30, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2013 – June 30, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2013 – March 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2012 – December 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2012 – September 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2011 – June 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2011 – March 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2010 – September 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2010 – June 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2010 – March 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
October 1, 2004 – December 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
April 1, 2004 – June 30, 2004
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2025 – October 16, 2025 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| May 1, 2015 – May 31, 2015 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| February 1, 2015 – February 28, 2015 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| January 1, 2015 – March 31, 2015 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2014 – December 31, 2014 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| September 1, 2014 – September 30, 2014 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| July 1, 2014 – September 30, 2014 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2014 – March 31, 2014 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2013 – December 31, 2013 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| July 1, 2013 – September 30, 2013 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2013 – June 30, 2013 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2013 – March 31, 2013 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2012 – March 31, 2012 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2011 – March 31, 2011 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2010 – June 30, 2010 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2010 – March 31, 2010 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2004 – December 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- October 16, 2025State Compliance achieved1 linked violation
- August 5, 2025State Consumer Confidence Report Follow-up Notice1 linked violation
- August 5, 2025State Violation/Reminder Notice1 linked violation
- May 30, 2016State Compliance achieved1 linked violation
- February 28, 2016State Compliance achieved1 linked violation
- September 30, 2015State Compliance achieved1 linked violation
- July 22, 2015State Compliance achieved20 linked violations
- June 18, 2015State Public Notification received1 linked violation
- June 11, 2015State Public Notification requested1 linked violation
- June 11, 2015State Violation/Reminder Notice1 linked violation
- March 20, 2015State Public Notification received1 linked violation
- March 12, 2015State Public Notification requested1 linked violation
- March 12, 2015State Violation/Reminder Notice1 linked violation
- March 6, 2015State Public Notification received1 linked violation
- March 6, 2015State Public Notification received1 linked violation
- February 23, 2015State Public Notification requested1 linked violation
- February 23, 2015State Public Notification requested1 linked violation
- February 23, 2015State Violation/Reminder Notice1 linked violation
- February 23, 2015State Violation/Reminder Notice1 linked violation
- October 31, 2014State Public Notification received1 linked violation
- October 6, 2014State Public Notification received1 linked violation
- October 3, 2014State Violation/Reminder Notice1 linked violation
- October 3, 2014State Public Notification requested1 linked violation
- September 16, 2014State Public Notification requested1 linked violation
- September 16, 2014State Violation/Reminder Notice1 linked violation
- April 23, 2014State Public Notification received1 linked violation
- March 20, 2014State Violation/Reminder Notice1 linked violation
- March 20, 2014State Public Notification requested1 linked violation
- January 22, 2014State Public Notification received1 linked violation
- December 20, 2013State Violation/Reminder Notice1 linked violation
- December 20, 2013State Public Notification requested1 linked violation
- November 14, 2013State Public Notification received1 linked violation
- October 15, 2013State Public Notification requested1 linked violation
- October 15, 2013State Violation/Reminder Notice1 linked violation
- August 19, 2013State Compliance achieved4 linked violations
- June 26, 2013State Public Notification received1 linked violation
- May 28, 2013State Public Notification requested1 linked violation
- May 28, 2013State Violation/Reminder Notice1 linked violation
- February 26, 2013State Violation/Reminder Notice1 linked violation
- February 26, 2013State Public Notification requested1 linked violation
- January 8, 2013State Public Notification received1 linked violation
- December 7, 2012State Violation/Reminder Notice1 linked violation
- December 7, 2012State Public Notification requested1 linked violation
- September 26, 2012State Public Notification received1 linked violation
- September 17, 2012State Violation/Reminder Notice1 linked violation
- September 17, 2012State Public Notification requested2 linked violations
- June 28, 2012State Public Notification received1 linked violation
- May 24, 2012State Violation/Reminder Notice1 linked violation
- May 24, 2012State Public Notification requested1 linked violation
- May 3, 2012State Public Notification received1 linked violation
- April 10, 2012State Public Notification requested1 linked violation
- April 10, 2012State Violation/Reminder Notice22 linked violations
- November 17, 2011State Violation/Reminder Notice1 linked violation
- November 15, 2011State Public Notification requested2 linked violations
- September 30, 2011State Violation/Reminder Notice1 linked violation
- September 30, 2011State Public Notification requested2 linked violations
- June 30, 2011State Public Notification received1 linked violation
- June 22, 2011State Violation/Reminder Notice1 linked violation
- June 22, 2011State Public Notification requested1 linked violation
- April 27, 2011State Public Notification received1 linked violation
- April 15, 2011State Public Notification requested1 linked violation
- April 15, 2011State Violation/Reminder Notice1 linked violation
- January 27, 2011State Public Notification received2 linked violations
- December 31, 2010State Compliance achieved1 linked violation
- December 29, 2010State Public Notification requested1 linked violation
- December 29, 2010State Violation/Reminder Notice1 linked violation
- November 23, 2010State Public Notification received4 linked violations
- November 18, 2010State Public Notification requested1 linked violation
- July 28, 2010State Public Notification received2 linked violations
- July 21, 2010State Violation/Reminder Notice2 linked violations
- March 29, 2010State Violation/Reminder Notice2 linked violations
- March 29, 2010State Public Notification requested2 linked violations
- January 25, 2010State Public Notification received3 linked violations
- May 9, 2007State Administrative/Compliance Order without penalty issued4 linked violations
- February 2, 2005State Public Notification received7 linked violations
- November 29, 2004State Violation/Reminder Notice3 linked violations
- October 1, 2004State Public Notification received3 linked violations
- October 30, 2000State Compliance achieved1 linked violation
- March 30, 2000State Compliance achieved1 linked violation
- October 29, 1999State Public Notification received1 linked violation
- October 22, 1999State Public Notification requested1 linked violation
- October 22, 1999State Violation/Reminder Notice1 linked violation
- September 30, 1999State Compliance achieved1 linked violation
- May 6, 1999State Public Notification received1 linked violation
- May 4, 1999State Violation/Reminder Notice1 linked violation
- May 4, 1999State Public Notification requested1 linked violation
- September 30, 1998State Public Notification requested2 linked violations
Common questions
Is BELLWOOD, VILLAGE OF required to publish a Consumer Confidence Report?
- Yes. BELLWOOD, 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 BELLWOOD, VILLAGE OF’s next Consumer Confidence Report due?
- BELLWOOD, VILLAGE OF’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BELLWOOD, VILLAGE OF have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BELLWOOD, 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
NICKOLITE, PAUL
402-367-2063
BELLWOOD, NE 68624-0188