DYERSVILLE, IA · Dubuque County
DYERSVILLE MUNICIPAL WATER CO Water System
Consumer Confidence Report status
DYERSVILLE MUNICIPAL WATER CO 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 DYERSVILLE MUNICIPAL WATER CO.
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 Iowa’s official records. Always confirm current status with Iowa before making decisions based on this information.
System facts
- System ID (PWSID)
- IA3130091
- System type
- Community Water System
- Population served
- 4,477
- Service connections
- 2,085
- Ownership
- local government
- Water source
- groundwater (wells)
DYERSVILLE MUNICIPAL WATER CO is one of 91 community water systems in Iowa in the 3,301 to 10,000 people size category, serving 4,477 people from groundwater.
As of August 1, 2026, its federal record holds 12 entries between 1992 and 2016, all of which EPA lists as closed. Nothing has been added since 2016.
Of the 12, 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 the Radionuclides and Revised Rad Rule, inorganic chemicals, and volatile organic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2016 – September 30, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2015 – December 31, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2015 – September 30, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2015 – June 30, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2015 – March 31, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedNitrate
March 1, 1994 – March 31, 1994
ResolvedMonitoring, Regular
—Xylenes, Total
July 1, 1993 – September 30, 1993
ResolvedMonitoring, Regular
—Nitrate
January 1, 1992 – March 31, 1992
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2016 – September 30, 2016 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2015 – December 31, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2015 – September 30, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2015 – June 30, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2015 – March 31, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2012 – March 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2007 – September 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| March 1, 1994 – March 31, 1994 | Maximum Contaminant Level Violation, Single Sample | Nitrate | Health-based | Resolved |
| July 1, 1993 – September 30, 1993 | Monitoring, Regular | Xylenes, Total | — | Resolved |
| January 1, 1992 – March 31, 1992 | Monitoring, Regular | Nitrate | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- May 29, 2024State Compliance achieved3 linked violations
- February 20, 2017State Formal Notice of Violation issued3 linked violations
- December 5, 2016State Compliance achieved3 linked violations
- December 5, 2016State Compliance achieved3 linked violations
- December 5, 2016State Compliance achieved35 linked violations
- December 5, 2016State Compliance achieved2 linked violations
- February 9, 2016State Formal Notice of Violation issued4 linked violations
- September 4, 2015State Public Notification requested2 linked violations
- March 23, 2015State Public Notification received3 linked violations
- September 18, 2014State Public Notification received3 linked violations
- August 25, 2014State Formal Notice of Violation issued3 linked violations
- March 13, 2014State Administrative/Compliance Order without penalty issued3 linked violations
- March 13, 2014State Administrative/Compliance Order without penalty issued3 linked violations
- March 13, 2014State Administrative/Compliance Order without penalty issued2 linked violations
- February 12, 2014State Public Notification requested2 linked violations
- December 12, 2013State Formal Notice of Violation issued4 linked violations
- August 1, 2013State Administrative/Compliance Order without penalty issued4 linked violations
- August 1, 2013State Administrative/Compliance Order without penalty issued3 linked violations
- August 1, 2013State Administrative/Compliance Order without penalty issued3 linked violations
- March 9, 2012State Administrative/Compliance Order without penalty issued3 linked violations
- January 26, 2012State Public Notification requested4 linked violations
- March 14, 2007State Public Notification received4 linked violations
- February 22, 2007State Bilateral Compliance Agreement signed3 linked violations
- November 18, 1996State Formal Notice of Violation issued1 linked violation
- November 18, 1996State Public Notification requested3 linked violations
- August 1, 1995State Compliance achieved1 linked violation
- August 1, 1995State Compliance achieved4 linked violations
- August 1, 1995State Compliance achieved2 linked violations
- July 11, 1995State Public Notification requested1 linked violation
- June 16, 1995State Formal Notice of Violation issued1 linked violation
- June 16, 1995State Public Notification requested1 linked violation
- March 23, 1995State Public Notification received4 linked violations
- January 20, 1995State Public Notification requested1 linked violation
- January 20, 1995State Formal Notice of Violation issued1 linked violation
- January 20, 1995State Public Notification requested4 linked violations
- June 27, 1994State Bilateral Compliance Agreement signed2 linked violations
- June 27, 1994State Compliance achieved2 linked violations
- June 27, 1994State Bilateral Compliance Agreement signed3 linked violations
- June 27, 1994State Compliance achieved1 linked violation
- June 27, 1994State Compliance achieved10 linked violations
- June 27, 1994State Compliance achieved6 linked violations
- June 27, 1994State Bilateral Compliance Agreement signed13 linked violations
- June 21, 1994State Public Notification requested3 linked violations
- December 23, 1993State Public Notification received2 linked violations
- December 1, 1993State Formal Notice of Violation issued7 linked violations
- November 19, 1993State Public Notification requested8 linked violations
- November 19, 1993State Formal Notice of Violation issued1 linked violation
- November 19, 1993State Public Notification requested1 linked violation
- November 19, 1993State Public Notification requested2 linked violations
- March 9, 1993State Compliance achieved2 linked violations
- March 3, 1993State Public Notification received3 linked violations
- June 11, 1992State Compliance achieved1 linked violation
- June 10, 1992State Public Notification received1 linked violation
- May 19, 1992State Formal Notice of Violation issued3 linked violations
- May 19, 1992State Public Notification requested3 linked violations
- May 19, 1992State Formal Notice of Violation issued2 linked violations
- May 19, 1992State Public Notification requested5 linked violations
Common questions
Is DYERSVILLE MUNICIPAL WATER CO required to publish a Consumer Confidence Report?
- Yes. DYERSVILLE MUNICIPAL WATER CO 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 DYERSVILLE MUNICIPAL WATER CO’s next Consumer Confidence Report due?
- DYERSVILLE MUNICIPAL WATER CO’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does DYERSVILLE MUNICIPAL WATER CO have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for DYERSVILLE MUNICIPAL WATER CO.
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
DYERSVILLE MUNICIPAL WATER CO
563-875-7724
DYERSVILLE, IA 52040