Henning, MN · Otter Tail County
Battle Lake Mobile Home Park Water System
Consumer Confidence Report status
Battle Lake Mobile Home Park 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 Battle Lake Mobile Home Park.
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)
- MN1560004
- System type
- Community Water System
- Population served
- 31
- Service connections
- 24
- Ownership
- privately owned
- Water source
- groundwater (wells)
Battle Lake Mobile Home Park is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 31 people from groundwater.
As of August 1, 2026, its federal record holds 5 entries between 2006 and 2020, all of which EPA lists as closed. Nothing has been added since 2020.
Of the 5, 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 Total Coliform Rules and inorganic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedNitrate
April 1, 2020 – June 30, 2020
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
October 1, 2009 – December 23, 2009
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedNitrate
August 23, 2006 – January 9, 2008
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2020 – June 30, 2020 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
| October 1, 2009 – December 23, 2009 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| August 23, 2006 – January 9, 2008 | Maximum Contaminant Level Violation, Average | Nitrate | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- October 1, 2021State Compliance achieved1 linked violation
- June 23, 2021State Compliance achieved1 linked violation
- June 23, 2021State Compliance achieved1 linked violation
- June 23, 2021State Compliance achieved1 linked violation
- June 23, 2021State Compliance achieved1 linked violation
- June 23, 2021State Compliance achieved1 linked violation
- February 23, 2021State Public Notification requested1 linked violation
- February 23, 2021State Formal Notice of Violation issued1 linked violation
- August 14, 2020State Public Notification requested1 linked violation
- August 14, 2020State Formal Notice of Violation issued6 linked violations
- August 14, 2020State Compliance Meeting conducted1 linked violation
- August 10, 2020State Formal Notice of Violation issued1 linked violation
- July 14, 2020State Formal Notice of Violation issued1 linked violation
- July 14, 2020State Public Notification requested1 linked violation
- July 14, 2020State Compliance Meeting conducted1 linked violation
- March 13, 2020State Compliance Meeting conducted9 linked violations
- December 18, 2019State Public Notification received1 linked violation
- November 20, 2019State Formal Notice of Violation issued1 linked violation
- November 20, 2019State Public Notification requested1 linked violation
- November 20, 2019State Compliance Meeting conducted1 linked violation
- September 6, 2019State Public Notification received1 linked violation
- August 28, 2019State Compliance Meeting conducted1 linked violation
- August 28, 2019State Public Notification requested1 linked violation
- August 28, 2019State Formal Notice of Violation issued1 linked violation
- July 24, 2018State Formal Notice of Violation issued1 linked violation
- July 24, 2018State Public Notification requested1 linked violation
- July 23, 2018State Compliance achieved1 linked violation
- November 8, 2016State Formal Notice of Violation issued1 linked violation
- November 8, 2016State Public Notification requested1 linked violation
- October 10, 2016State Compliance achieved1 linked violation
- September 20, 2016State Violation/Reminder Notice1 linked violation
- February 17, 2013State Public Notification received1 linked violation
- December 17, 2012State Compliance achieved1 linked violation
- September 28, 2012State Compliance Meeting conducted1 linked violation
- September 28, 2012State Formal Notice of Violation issued1 linked violation
- September 28, 2012State Public Notification requested2 linked violations
- September 28, 2012State Technical Assistance Visit1 linked violation
- April 2, 2012State Compliance achieved2 linked violations
- November 1, 2011State Violation/Reminder Notice1 linked violation
- August 31, 2011State Violation/Reminder Notice1 linked violation
- June 20, 2011State Violation/Reminder Notice2 linked violations
- December 31, 2009State Public Notification received1 linked violation
- December 23, 2009State Compliance achieved5 linked violations
- December 10, 2009State Public Notification requested1 linked violation
- December 10, 2009State Technical Assistance Visit1 linked violation
- December 10, 2009State Compliance Meeting conducted1 linked violation
- December 10, 2009State Formal Notice of Violation issued1 linked violation
- August 4, 2009State Violation/Reminder Notice4 linked violations
- July 14, 2009State Compliance achieved2 linked violations
- May 19, 2009State Violation/Reminder Notice3 linked violations
- January 30, 2009State Public Notification received1 linked violation
- January 13, 2009State Public Notification requested1 linked violation
- January 13, 2009State Formal Notice of Violation issued1 linked violation
- January 12, 2009State Compliance achieved3 linked violations
- December 19, 2008State Violation/Reminder Notice1 linked violation
- December 8, 2008State Violation/Reminder Notice1 linked violation
- January 9, 2008State Compliance achieved1 linked violation
- February 27, 2007State Compliance achieved1 linked violation
- January 30, 2007State Public Notification received2 linked violations
- January 11, 2007State Formal Notice of Violation issued1 linked violation
- December 7, 2006State Violation/Reminder Notice1 linked violation
- September 13, 2006State Formal Notice of Violation issued8 linked violations
Common questions
Is Battle Lake Mobile Home Park required to publish a Consumer Confidence Report?
- Yes. Battle Lake Mobile Home Park 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 Battle Lake Mobile Home Park’s next Consumer Confidence Report due?
- Battle Lake Mobile Home Park’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Battle Lake Mobile Home Park have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for Battle Lake Mobile Home Park.
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
Battle Lake Mobile Home Park
Phone not on record
Henning, MN 56551