RIVERSIDE SUD
PWSID: TX2360010 · Riverside, TX · Serves 6,246 people
According to EPA Safe Drinking Water Information System (SDWIS), RIVERSIDE SUD (PWSID TX2360010) in Riverside, TX is listed as a CWS water system covering about 6,246 people. The same extract lists 120 health-based violation records spanning 2014-2025. Those 120 health-based rows for RIVERSIDE SUD cover contaminants such as TTHM; they remain historical EPA registry entries, not a current compliance or drinkability score.
RIVERSIDE SUD has 120 health-based violation records in this historical extract. Monitoring and reporting records are not included.
PlainEnviro's health-based SDWIS extract covers monitoring and reporting violations only -- it does not include unresolved enforcement actions in progress or corrective steps a utility has taken since the extract date. 1 distinct EPA contaminant code appears in this system's record, including TTHM. Recorded violations span 2014–2025. Day-to-day primacy enforcement for this system runs through the Texas drinking-water program, not EPA directly.
A historical health-based record does not necessarily describe current water quality or compliance. The most authoritative current source is the utility's annual Consumer Confidence Report. For enforcement history and corrective-action orders, consult EPA ECHO and the Texas state drinking-water program's public portal.
System Details
- EPA ID (PWSID)
- TX2360010
- System Type
- CWS
- Water Source
- Groundwater
- Location
- Riverside, TX
- Population Served
- 6,246
- Health Violations
- Yes (120)
What contaminants are in this water system?
| Contaminant | Violations | Health-Based |
|---|---|---|
| TTHM | 120 | 120 |
Violation History (120)
| Contaminant | Health | Date |
|---|---|---|
| TTHM | Yes | Oct 1, 2025 |
| TTHM | Yes | Jul 1, 2025 |
| TTHM | Yes | Apr 1, 2024 |
| TTHM | Yes | Apr 1, 2024 |
| TTHM | Yes | Apr 1, 2024 |
| TTHM | Yes | Apr 1, 2024 |
| TTHM | Yes | Apr 1, 2024 |
| TTHM | Yes | Apr 1, 2022 |
| TTHM | Yes | Apr 1, 2022 |
| TTHM | Yes | Apr 1, 2022 |
| TTHM | Yes | Apr 1, 2022 |
| TTHM | Yes | Apr 1, 2022 |
| TTHM | Yes | Jan 1, 2022 |
| TTHM | Yes | Jan 1, 2022 |
| TTHM | Yes | Jan 1, 2022 |
| TTHM | Yes | Jan 1, 2022 |
| TTHM | Yes | Jan 1, 2022 |
| TTHM | Yes | Oct 1, 2021 |
| TTHM | Yes | Oct 1, 2021 |
| TTHM | Yes | Oct 1, 2021 |
| TTHM | Yes | Oct 1, 2021 |
| TTHM | Yes | Oct 1, 2021 |
| TTHM | Yes | Jul 1, 2021 |
| TTHM | Yes | Jul 1, 2021 |
| TTHM | Yes | Jul 1, 2021 |
| TTHM | Yes | Jul 1, 2021 |
| TTHM | Yes | Jul 1, 2021 |
| TTHM | Yes | Jan 1, 2021 |
| TTHM | Yes | Jan 1, 2021 |
| TTHM | Yes | Jan 1, 2021 |
| TTHM | Yes | Oct 1, 2020 |
| TTHM | Yes | Oct 1, 2020 |
| TTHM | Yes | Oct 1, 2020 |
| TTHM | Yes | Jan 1, 2020 |
| TTHM | Yes | Jan 1, 2020 |
| TTHM | Yes | Jan 1, 2020 |
| TTHM | Yes | Oct 1, 2019 |
| TTHM | Yes | Oct 1, 2019 |
| TTHM | Yes | Oct 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Jul 1, 2019 |
| TTHM | Yes | Apr 1, 2019 |
| TTHM | Yes | Apr 1, 2019 |
| TTHM | Yes | Apr 1, 2019 |
| TTHM | Yes | Jan 1, 2019 |
| TTHM | Yes | Jan 1, 2019 |
| TTHM | Yes | Jan 1, 2019 |
| TTHM | Yes | Oct 1, 2018 |
| TTHM | Yes | Oct 1, 2018 |
| TTHM | Yes | Oct 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Jul 1, 2018 |
| TTHM | Yes | Apr 1, 2018 |
| TTHM | Yes | Apr 1, 2018 |
| TTHM | Yes | Apr 1, 2018 |
| TTHM | Yes | Jan 1, 2018 |
| TTHM | Yes | Jan 1, 2018 |
| TTHM | Yes | Jan 1, 2018 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Oct 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Jul 1, 2017 |
| TTHM | Yes | Apr 1, 2017 |
| TTHM | Yes | Apr 1, 2017 |
| TTHM | Yes | Apr 1, 2017 |
| TTHM | Yes | Jan 1, 2017 |
| TTHM | Yes | Jan 1, 2017 |
| TTHM | Yes | Jan 1, 2017 |
| TTHM | Yes | Oct 1, 2016 |
| TTHM | Yes | Oct 1, 2016 |
| TTHM | Yes | Oct 1, 2016 |
| TTHM | Yes | Jul 1, 2016 |
| TTHM | Yes | Jul 1, 2016 |
| TTHM | Yes | Jul 1, 2016 |
| TTHM | Yes | Apr 1, 2016 |
| TTHM | Yes | Apr 1, 2016 |
| TTHM | Yes | Apr 1, 2016 |
| TTHM | Yes | Jan 1, 2016 |
| TTHM | Yes | Jan 1, 2016 |
| TTHM | Yes | Jan 1, 2016 |
| TTHM | Yes | Oct 1, 2015 |
| TTHM | Yes | Oct 1, 2015 |
| TTHM | Yes | Oct 1, 2015 |
| TTHM | Yes | Oct 1, 2015 |
Frequently Asked Questions
What does EPA SDWIS list for RIVERSIDE SUD?
How many people does RIVERSIDE SUD serve?
What violations does RIVERSIDE SUD have?
What contaminants have been found in RIVERSIDE SUD water?
Compare beyond Texas
Nationwide peers by violations & population served
Cross-state SDWIS systems nearest RIVERSIDE SUD on cumulative violation count (120) and EPA-reported population served (6,246). Violation-count peers include LANARE COMMUNITY SERVICES DIST, CARUTHERS COMM SERV DIST, KETTLEMAN CITY CSD. Population peers include PURISSIMA HILLS WATER DISTRICT, RANDALL COMMUNITY WATER DISTRICT, SOUTH ELIZABETHTON U.D..
Similar violation count
Nearest cross-state community systems (500+ served) by SDWIS violations on record.
Similar population served
Nearest cross-state systems by EPA SDWIS population_served (same 500+ gate).
Nearby Water Systems
Explore More
About This Data
RIVERSIDE SUD (TX2360010) is drawn from EPA SDWIS. Nearby county systems in this extract include CITY OF HUNTSVILLE; SANTA FE UTILITY; TDCJ BETO UNIT; TDCJ COFFIELD UNIT. Health-based rows (120 MCL/TT) are historical registry state, not a current drinkability score.
Source: U.S. Environmental Protection Agency, SDWIS Federal Reporting Services
Read our methodology - how this data is sourced, computed, and verified.