Rush City, MN · Chisago County
Shorewood Park Water System
Consumer Confidence Report status
Shorewood 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 1 item for Shorewood Park that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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)
- MN1130021
- System type
- Community Water System
- Population served
- 85
- Service connections
- 33
- Ownership
- privately owned
- Water source
- groundwater (wells)
Shorewood Park is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 85 people from groundwater.
As of August 1, 2026, its federal record holds 23 entries between 2009 and 2026, of which 1 remains open; none are health-based.
Of the 23, 5 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, the Total Coliform Rules, and the Public Notice Rule and Revised PN Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2026 – March 31, 2026
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2025 – December 31, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2025 – September 30, 2025
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
March 19, 2025 – February 22, 2025
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2025 – March 31, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2024 – December 31, 2024
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
August 19, 2024
UnaddressedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2024 – September 30, 2024
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
June 22, 2024 – June 17, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2024 – June 30, 2024
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2024 – March 31, 2024
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2023 – December 31, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2023 – September 30, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2023 – March 31, 2023
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2022 – December 31, 2022
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2022 – March 31, 2022
ArchivedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
October 1, 2021 – December 31, 2021
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2021 – June 30, 2021
ArchivedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
October 1, 2018 – December 31, 2018
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2018 – September 30, 2018
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
July 1, 2015 – September 30, 2015
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
July 1, 2009 – September 30, 2009
Resolved
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2026 – March 31, 2026 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2025 – December 31, 2025 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| July 1, 2025 – September 30, 2025 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| March 19, 2025 – February 22, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2025 – March 31, 2025 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2024 – December 31, 2024 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| August 19, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| July 1, 2024 – September 30, 2024 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| June 22, 2024 – June 17, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| April 1, 2024 – June 30, 2024 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| January 1, 2024 – March 31, 2024 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2023 – December 31, 2023 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| July 1, 2023 – September 30, 2023 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| January 1, 2023 – March 31, 2023 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2022 – December 31, 2022 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| January 1, 2022 – March 31, 2022 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2021 – December 31, 2021 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| April 1, 2021 – June 30, 2021 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 2018 – December 31, 2018 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| July 1, 2018 – September 30, 2018 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2015 – September 30, 2015 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
Enforcement actions
- March 18, 2026State Formal Notice of Violation issued1 linked violation
- March 18, 2026State Public Notification requested1 linked violation
- March 18, 2026State Compliance Meeting conducted1 linked violation
- January 6, 2026State Public Notification received1 linked violation
- December 5, 2025State Public Notification requested1 linked violation
- December 5, 2025State Compliance Meeting conducted1 linked violation
- December 5, 2025State Formal Notice of Violation issued1 linked violation
- October 4, 2025State Public Notification received1 linked violation
- September 30, 2025State Formal Notice of Violation issued1 linked violation
- September 30, 2025State Public Notification requested1 linked violation
- September 30, 2025State Compliance Meeting conducted1 linked violation
- July 2, 2025State Public Notification received1 linked violation
- May 27, 2025State Compliance Meeting conducted1 linked violation
- May 27, 2025State Public Notification requested1 linked violation
- May 27, 2025State Formal Notice of Violation issued1 linked violation
- May 13, 2025State Public Notification received1 linked violation
- March 6, 2025State Public Notification requested1 linked violation
- March 6, 2025State Compliance Meeting conducted1 linked violation
- March 6, 2025State Formal Notice of Violation issued1 linked violation
- February 22, 2025State Public Notification received1 linked violation
- February 22, 2025State Compliance achieved1 linked violation
- February 7, 2025State Formal Notice of Violation issued1 linked violation
- February 7, 2025State Compliance Meeting conducted1 linked violation
- February 7, 2025State Public Notification requested1 linked violation
- January 16, 2025State Formal Notice of Violation issued1 linked violation
- January 14, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- January 14, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- January 12, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- January 12, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- January 12, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- January 12, 2025State Administrative/Compliance Order with penalty issued1 linked violation
- December 17, 2024State Public Notification requested1 linked violation
- December 17, 2024State Compliance Meeting conducted1 linked violation
- December 17, 2024State Formal Notice of Violation issued1 linked violation
- October 22, 2024State Formal Notice of Violation issued1 linked violation
- July 10, 2024State Compliance Meeting conducted1 linked violation
- July 10, 2024State Public Notification requested1 linked violation
- July 10, 2024State Formal Notice of Violation issued1 linked violation
- June 17, 2024State Public Notification received1 linked violation
- June 17, 2024State Compliance achieved1 linked violation
- May 13, 2024State Formal Notice of Violation issued1 linked violation
- May 13, 2024State Public Notification requested1 linked violation
- May 13, 2024State Compliance Meeting conducted1 linked violation
- April 25, 2024State Formal Notice of Violation issued1 linked violation
- March 1, 2024State Public Notification requested1 linked violation
- March 1, 2024State Compliance Meeting conducted1 linked violation
- March 1, 2024State Formal Notice of Violation issued1 linked violation
- January 8, 2024State Compliance Meeting conducted1 linked violation
- January 8, 2024State Formal Notice of Violation issued1 linked violation
- January 8, 2024State Public Notification requested1 linked violation
- April 27, 2023State Public Notification requested1 linked violation
- April 27, 2023State Compliance Meeting conducted1 linked violation
- April 27, 2023State Formal Notice of Violation issued1 linked violation
- March 21, 2023State Formal Notice of Violation issued1 linked violation
- March 21, 2023State Public Notification requested1 linked violation
- March 21, 2023State Compliance Meeting conducted1 linked violation
- July 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
- July 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
- April 4, 2022State Formal Notice of Violation issued1 linked violation
- April 4, 2022State Formal Notice of Violation issued1 linked violation
- April 4, 2022State Public Notification requested1 linked violation
- April 4, 2022State Compliance Meeting conducted1 linked violation
- April 4, 2022State Public Notification requested1 linked violation
- April 4, 2022State Compliance Meeting conducted1 linked violation
- March 11, 2022State Public Notification requested1 linked violation
- March 11, 2022State Formal Notice of Violation issued1 linked violation
- February 7, 2022State Compliance achieved1 linked violation
- July 8, 2021State Compliance Meeting conducted1 linked violation
- July 8, 2021State Formal Notice of Violation issued1 linked violation
- July 8, 2021State Public Notification requested1 linked violation
- December 3, 2019State Compliance achieved1 linked violation
- January 22, 2019State Public Notification requested1 linked violation
- January 22, 2019State Formal Notice of Violation issued1 linked violation
- January 7, 2019State Compliance achieved1 linked violation
- November 30, 2018State Public Notification received1 linked violation
- November 6, 2018State Compliance Meeting conducted1 linked violation
- November 6, 2018State Formal Notice of Violation issued1 linked violation
- November 6, 2018State Public Notification requested1 linked violation
- October 15, 2015State Public Notification requested1 linked violation
- October 1, 2015State Compliance achieved1 linked violation
- September 10, 2015State Violation/Reminder Notice1 linked violation
- February 25, 2015State Compliance achieved1 linked violation
- January 16, 2015State Formal Notice of Violation issued1 linked violation
- December 16, 2014State Violation/Reminder Notice1 linked violation
- June 23, 2014State Compliance achieved2 linked violations
- September 17, 2012State Public Notification received2 linked violations
- July 27, 2012State Public Notification requested1 linked violation
- July 27, 2012State Formal Notice of Violation issued1 linked violation
- June 13, 2012State Violation/Reminder Notice1 linked violation
- April 30, 2012State Compliance achieved3 linked violations
- April 24, 2012State Public Notification received2 linked violations
- April 13, 2012State Formal Notice of Violation issued1 linked violation
- April 13, 2012State Public Notification requested1 linked violation
- December 18, 2009State Public Notification requested5 linked violations
- February 21, 2006State Public Notification received1 linked violation
- February 6, 2006State Formal Notice of Violation issued3 linked violations
- February 6, 2006State Technical Assistance Visit2 linked violations
- February 6, 2006State Public Notification requested2 linked violations
- December 31, 2000State Compliance achieved2 linked violations
Common questions
Is Shorewood Park required to publish a Consumer Confidence Report?
- Yes. Shorewood 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 Shorewood Park’s next Consumer Confidence Report due?
- Shorewood Park’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Shorewood Park have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for Shorewood Park that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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
Shorewood Park Association
6517641468
Rush City, MN 55069