Regent City of

PWSID: ND2100816

System Details

Population Served160
Service Connections168
Water SourceSurface Water Purchased
System TypeCommunity Water System
OwnerLocal Government
StatusActive
CityRegent
Zip Code58650

Areas Served

  • Regent, Hettinger County

Lead & Copper Testing

ContaminantLevelEPA Action LevelStatus
Lead (90th percentile)0.0007 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0000 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0000 mg/L0.015 mg/LBelow Action Level
Lead (90th percentile)0.0000 mg/L0.015 mg/LBelow Action Level

2 Active Violations

ContaminantViolationDateHealth-BasedStatus
2024-10-02Open
2022-11-09Open

Violation History (41 total)

ContaminantViolationDateHealth-BasedStatus
2025-07-02Returned to Compliance
2025-04-01 MajorAcknowledged
2025-04-01 MajorAcknowledged
2024-07-01 MajorReturned to Compliance
2024-07-01 MajorAcknowledged
2024-07-01 MajorReturned to Compliance
2024-07-01 MajorReturned to Compliance
2024-07-01 MajorAcknowledged
2024-07-01 MajorReturned to Compliance
2024-07-01 MajorAcknowledged
2022-12-01 MajorReturned to Compliance
2022-12-01 MajorAcknowledged
2022-12-01 MajorReturned to Compliance
2022-10-01 MajorReturned to Compliance
2022-10-01 MajorReturned to Compliance
2022-10-01 MajorAcknowledged
2022-10-01 MajorReturned to Compliance
2019-12-03Returned to Compliance
2019-10-02Returned to Compliance
2019-09-01 MajorReturned to Compliance
2019-07-01Returned to Compliance
2019-07-01 MajorReturned to Compliance
2018-10-02Returned to Compliance
2018-10-02Returned to Compliance
2018-07-01Returned to Compliance
2017-10-01 MajorReturned to Compliance
2017-09-01 MajorReturned to Compliance
2017-07-01 MajorReturned to Compliance
2016-10-02Returned to Compliance
2016-07-01Returned to Compliance
2015-10-02Returned to Compliance
2015-07-01Returned to Compliance
2013-08-08Returned to Compliance
2012-10-02Returned to Compliance
2012-07-01Returned to Compliance
2011-08-21Returned to Compliance
2011-06-15Returned to Compliance
2010-11-13Returned to Compliance
2009-08-20Returned to Compliance