IOWA CITY, IA · Johnson County
IOWA CITY REGENCY MOBILE HOME COMMUNITY Water System
Consumer Confidence Report status
IOWA CITY REGENCY MOBILE HOME COMMUNITY 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 IOWA CITY REGENCY MOBILE HOME COMMUNITY.
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 Iowa’s official records. Always confirm current status with Iowa before making decisions based on this information.
System facts
- System ID (PWSID)
- IA5225673
- System type
- Community Water System
- Population served
- 225
- Service connections
- 90
- Ownership
- privately owned
- Water source
- groundwater (wells)
IOWA CITY REGENCY MOBILE HOME COMMUNITY is one of 1,221 community water systems in Iowa in the 500 or fewer people size category, serving 225 people from groundwater.
As of August 1, 2026, its federal record holds 38 entries between 1980 and 2017, all of which EPA lists as closed. Nothing has been added since 2017.
Of the 38, 21 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 inorganic chemicals, the Radionuclides and Revised Rad Rule, and the Groundwater Rule.
Violation history
Treatment Technique (SWTR and GWR)
Health-basedGroundwater Rule
January 1, 2017 – December 31, 2017
ResolvedMonitoring, Regular
—Mercury
October 1, 2016 – September 30, 2025
ArchivedMonitoring, Regular
—Cadmium
October 1, 2016 – September 30, 2025
ArchivedMonitoring, Regular
—Beryllium, Total
October 1, 2016 – September 30, 2025
ArchivedTreatment Technique (SWTR and GWR)
Health-basedGroundwater Rule
October 1, 2016 – October 31, 2016
ResolvedMonitoring, Regular
—Thallium, Total
October 1, 2016 – September 30, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedCombined Radium (-226 and -228)
January 1, 1996 – December 31, 1999
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
April 1, 1991 – April 30, 1991
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 1989 – January 16, 1990
ResolvedMonitoring, Regular
—Selenium
January 1, 1987 – December 31, 1989
ResolvedMonitoring, Regular
—Barium
January 1, 1987 – December 31, 1989
ResolvedMonitoring, Regular
—Cadmium
January 1, 1987 – December 31, 1989
ResolvedMonitoring, Regular
—Chromium
January 1, 1987 – December 31, 1989
ResolvedMonitoring, Regular
—Fluoride
January 1, 1987 – December 31, 1989
ResolvedMonitoring, Regular
—Mercury
January 1, 1987 – December 31, 1989
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedCombined Radium (-226 and -228)
January 1, 1986 – March 31, 1986
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1985 – September 30, 1986
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1984 – September 30, 1985
ArchivedMonitoring, Regular
—Arsenic
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Mercury
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Nitrate
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Selenium
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Fluoride
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Combined Radium (-226 and -228)
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Chromium
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Cadmium
September 30, 1980 – September 29, 1983
ArchivedMonitoring, Regular
—Barium
September 30, 1980 – September 29, 1983
Archived
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2017 – December 31, 2017 | Treatment Technique (SWTR and GWR) | Groundwater Rule | Health-based | Resolved |
| October 1, 2016 – September 30, 2025 | Monitoring, Regular | Mercury | — | Archived |
| October 1, 2016 – September 30, 2025 | Monitoring, Regular | Cadmium | — | Archived |
| October 1, 2016 – September 30, 2025 | Monitoring, Regular | Beryllium, Total | — | Archived |
| October 1, 2016 – October 31, 2016 | Treatment Technique (SWTR and GWR) | Groundwater Rule | Health-based | Resolved |
| October 1, 2016 – September 30, 2025 | Monitoring, Regular | Thallium, Total | — | Archived |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2007 – September 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 1996 – December 31, 1999 | Maximum Contaminant Level Violation, Single Sample | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 1991 – April 30, 1991 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| October 1, 1989 – January 16, 1990 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Selenium | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Barium | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Cadmium | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Chromium | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Fluoride | — | Resolved |
| January 1, 1987 – December 31, 1989 | Monitoring, Regular | Mercury | — | Resolved |
| January 1, 1986 – March 31, 1986 | Maximum Contaminant Level Violation, Single Sample | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1985 – September 30, 1986 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| October 1, 1984 – September 30, 1985 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Arsenic | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Mercury | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Nitrate | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Selenium | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Fluoride | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Chromium | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Cadmium | — | Archived |
| September 30, 1980 – September 29, 1983 | Monitoring, Regular | Barium | — | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- November 24, 2025State Formal Notice of Violation issued1 linked violation
- November 24, 2025State Public Notification requested1 linked violation
- May 19, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- May 19, 2025State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- September 30, 2018State Compliance achieved1 linked violation
- September 30, 2018State Compliance achieved1 linked violation
- February 21, 2018State Formal Notice of Violation issued1 linked violation
- November 7, 2016State Violation/Reminder Notice1 linked violation
- November 7, 2016State Formal Notice of Violation issued1 linked violation
- January 12, 2014State Compliance achieved1 linked violation
- November 27, 2013State Formal Notice of Violation issued1 linked violation
- November 27, 2013State Public Notification requested1 linked violation
- June 4, 2013State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 19, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- June 4, 2012State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- June 4, 2012State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 29, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- February 16, 2012State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- February 16, 2012State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- June 9, 2011State Administrative/Compliance Order with penalty issued2 linked violations
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- June 9, 2011State Administrative/Compliance Order with penalty issued1 linked violation
- May 8, 2007State Public Notification received2 linked violations
- April 9, 2007State Bilateral Compliance Agreement signed1 linked violation
- April 9, 2007State Bilateral Compliance Agreement signed3 linked violations
- March 23, 2007State Formal Notice of Violation issued2 linked violations
- March 23, 2007State Public Notification requested1 linked violation
- January 10, 2007State Public Notification received1 linked violation
- November 29, 2006State Formal Notice of Violation issued1 linked violation
- August 18, 2006State Formal Notice of Violation issued1 linked violation
- November 28, 2005State Compliance achieved1 linked violation
- September 27, 2005State Compliance achieved2 linked violations
- September 27, 2005State Compliance achieved3 linked violations
- September 27, 2005State Compliance achieved2 linked violations
- May 31, 2005State Public Notification received1 linked violation
- March 28, 2005State Public Notification requested3 linked violations
- March 28, 2005State Formal Notice of Violation issued2 linked violations
- March 7, 2005State Public Notification requested3 linked violations
- February 24, 2005State Violation/Reminder Notice2 linked violations
- January 24, 2003State Public Notification received1 linked violation
- October 24, 2002State Public Notification requested3 linked violations
- October 24, 2002State Formal Notice of Violation issued2 linked violations
- January 28, 2000State Formal Notice of Violation issued2 linked violations
- December 2, 1997State Public Notification received3 linked violations
- November 21, 1996State Compliance achieved1 linked violation
- November 18, 1996State Public Notification requested1 linked violation
- November 18, 1996State Formal Notice of Violation issued1 linked violation
- May 31, 1996State Compliance achieved7 linked violations
- January 20, 1995State Public Notification requested3 linked violations
- October 18, 1994State Public Notification received3 linked violations
- December 16, 1993State Compliance achieved1 linked violation
- June 14, 1991State Formal Notice of Violation issued2 linked violations
- June 14, 1991State Formal Notice of Violation issued2 linked violations
- May 2, 1991State Compliance achieved2 linked violations
- January 16, 1990State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- January 16, 1990State Compliance achieved1 linked violation
- January 16, 1990State Compliance achieved1 linked violation
- January 16, 1990State Compliance achieved8 linked violations
- January 16, 1990State Compliance achieved1 linked violation
- January 4, 1989State Compliance achieved1 linked violation
- August 11, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 11, 1988State Compliance achieved1 linked violation
- August 11, 1988State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 7, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 7, 1988State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- July 7, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 7, 1988State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 31, 1986State Bilateral Compliance Agreement signed1 linked violation
- February 15, 1986State Public Notification received1 linked violation
- January 15, 1986State Formal Notice of Violation issued1 linked violation
- January 15, 1986State Formal Notice of Violation issued1 linked violation
- March 1, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record
- February 16, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record
Common questions
Is IOWA CITY REGENCY MOBILE HOME COMMUNITY required to publish a Consumer Confidence Report?
- Yes. IOWA CITY REGENCY MOBILE HOME COMMUNITY 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 IOWA CITY REGENCY MOBILE HOME COMMUNITY’s next Consumer Confidence Report due?
- IOWA CITY REGENCY MOBILE HOME COMMUNITY’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does IOWA CITY REGENCY MOBILE HOME COMMUNITY have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for IOWA CITY REGENCY MOBILE HOME COMMUNITY.
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
IOWA CITY REGENCY MOBILE HOME COMMUNITY
319-471-8285
IOWA CITY, IA 52240