Trosky, MN · Pipestone County
Trosky Water System
Consumer Confidence Report status
Trosky 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 Trosky 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)
- MN1590008
- System type
- Community Water System
- Population served
- 86
- Service connections
- 40
- Ownership
- local government
- Water source
- groundwater (wells)
Trosky is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 86 people from groundwater.
As of August 1, 2026, its federal record holds 3 entries between 2019 and 2026, of which 1 remains open; none are health-based.
All 3 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 Lead and Copper Rule.
Violation history
Lead Consumer Notice
—Lead and Copper Rule
January 1, 2026 – December 31, 2025
ResolvedNotification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025
UnaddressedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2019 – August 6, 2020
Resolved
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2026 – December 31, 2025 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| July 2, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Unaddressed |
| October 1, 2019 – August 6, 2020 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
Enforcement actions
- December 31, 2025State Formal Notice of Violation issued1 linked violation
- December 31, 2025State Compliance achieved1 linked violation
- September 18, 2025State Violation/Reminder Notice1 linked violation
- July 28, 2025State Violation/Reminder Notice1 linked violation
- January 31, 2025State Formal Notice of Violation issued1 linked violation
- August 6, 2020State Compliance achieved1 linked violation
- January 16, 2020State Violation/Reminder Notice1 linked violation
- October 15, 2019State Public Notification requested2 linked violations
- October 15, 2019State Formal Notice of Violation issued2 linked violations
- October 14, 2019State Compliance achieved2 linked violations
- September 23, 2019State Violation/Reminder Notice2 linked violations
- September 17, 2019State Violation/Reminder Notice1 linked violation
- December 18, 2013State Compliance achieved2 linked violations
- November 20, 2013State Formal Notice of Violation issued1 linked violation
- November 1, 2013State Public Notification requested2 linked violations
- November 1, 2013State Formal Notice of Violation issued4 linked violations
- October 25, 2013State Compliance achieved7 linked violations
- September 19, 2013State Violation/Reminder Notice1 linked violation
- September 3, 2013State Violation/Reminder Notice2 linked violations
- December 10, 2012State Public Notification received3 linked violations
- November 16, 2012State Public Notification requested2 linked violations
- November 16, 2012State Formal Notice of Violation issued2 linked violations
- October 31, 2012State Compliance achieved1 linked violation
- October 8, 2012State Compliance achieved1 linked violation
- September 11, 2012State Violation/Reminder Notice1 linked violation
- November 24, 2010State Public Notification received4 linked violations
- November 22, 2010State Compliance achieved4 linked violations
- October 21, 2010State Public Notification requested2 linked violations
- October 21, 2010State Formal Notice of Violation issued2 linked violations
- September 10, 2010State Violation/Reminder Notice1 linked violation
- August 23, 2010State Public Notification received4 linked violations
- July 20, 2010State Formal Notice of Violation issued5 linked violations
- October 10, 2005State Compliance achieved3 linked violations
- May 31, 2005State Violation/Reminder Notice7 linked violations
- January 10, 2005State Formal Notice of Violation issued1 linked violation
- January 10, 2005State Public Notification requested1 linked violation
- December 15, 2004State Violation/Reminder Notice1 linked violation
- December 1, 2004State Violation/Reminder Notice1 linked violation
- July 31, 2001State Compliance achieved6 linked violations
- September 1, 2000State Violation/Reminder Notice8 linked violations
- July 15, 1997State Violation/Reminder Notice2 linked violations
- January 10, 1997State Violation/Reminder Notice1 linked violation
- January 10, 1997State Public Notification requested1 linked violation
- October 15, 1995State Violation/Reminder Notice1 linked violation
- January 15, 1995State Public Notification requested1 linked violation
- January 15, 1995State Formal Notice of Violation issued1 linked violation
- January 15, 1995State Violation/Reminder Notice1 linked violation
- October 15, 1994State Formal Notice of Violation issued1 linked violation
- October 15, 1994State Public Notification requested1 linked violation
- July 15, 1994State Public Notification requested1 linked violation
- July 15, 1994State Formal Notice of Violation issued1 linked violation
- July 15, 1994State Violation/Reminder Notice1 linked violation
- August 15, 1991State Violation/Reminder Notice1 linked violation
- August 15, 1991State Formal Notice of Violation issued1 linked violation
- August 15, 1991State Public Notification requested1 linked violation
- December 15, 1989State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 1984State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- September 30, 1983State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 1982State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 30, 1981State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
Common questions
Is Trosky required to publish a Consumer Confidence Report?
- Yes. Trosky 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 Trosky’s next Consumer Confidence Report due?
- Trosky’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does Trosky have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for Trosky 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
Trosky City Council
5073483097
Trosky, MN 56144