Is CRICKET HILL APARTMENTS required to publish a Consumer Confidence Report?

Yes. CRICKET HILL APARTMENTS 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 CRICKET HILL APARTMENTS’s next Consumer Confidence Report due?

CRICKET HILL APARTMENTS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

MATHEWS, VA · Mathews County

CRICKET HILL APARTMENTS Water System

Consumer Confidence Report status

CRICKET HILL APARTMENTS 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 CRICKET HILL APARTMENTS.

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 Virginia’s official records. Always confirm current status with Virginia before making decisions based on this information.

System facts

System ID (PWSID): VA4115455
System type: Community Water System
Population served: 88
Service connections: 30
Ownership: privately owned
Water source: groundwater (wells)

CRICKET HILL APARTMENTS is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, serving 88 people from groundwater.

As of August 1, 2026, EPA's published records contain no violations for this system.

Violation history

No violations on record for this system.

Enforcement actions

February 9, 2026State Public Notification requested8 linked violations
February 9, 2026State Public Notification requested4 linked violations
February 9, 2026State Formal Notice of Violation issued3 linked violations
September 23, 2025State Public Notification received4 linked violations
August 27, 2025State Compliance achieved1 linked violation
March 11, 2025State Formal Notice of Violation issued1 linked violation
March 11, 2025State Public Notification requested1 linked violation
March 11, 2025State Public Notification requested1 linked violation
September 9, 2022State Compliance achieved2 linked violations
August 30, 2022State Formal Notice of Violation issued1 linked violation
June 7, 2021State Compliance achieved2 linked violations
September 2, 2015State Public Notification received2 linked violations
August 28, 2015State Compliance achieved2 linked violations
March 31, 2014State Public Notification requested1 linked violation
February 3, 2014State Public Notification received2 linked violations
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved2 linked violations
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 14, 2014State Compliance achieved1 linked violation
January 9, 2014State Formal Notice of Violation issued2 linked violations
January 9, 2014State Public Notification requested1 linked violation
October 31, 2013State Public Notification received2 linked violations
October 25, 2013State Public Notification requested1 linked violation
October 25, 2013State Public Notification requested1 linked violation
October 25, 2013State Formal Notice of Violation issued1 linked violation
August 1, 2013State Public Notification received2 linked violations
July 17, 2013State Public Notification requested1 linked violation
July 17, 2013State Public Notification requested1 linked violation
June 26, 2013State Public Notification received2 linked violations
May 27, 2013State Formal Notice of Violation issued1 linked violation
May 27, 2013State Formal Notice of Violation issued1 linked violation
May 27, 2013State Public Notification requested1 linked violation
May 27, 2013State Public Notification requested1 linked violation
April 4, 2013State Formal Notice of Violation issued1 linked violation
April 4, 2013State Public Notification requested1 linked violation
April 4, 2013State Public Notification requested1 linked violation
October 28, 2011State Public Notification received1 linked violation
October 18, 2011State Compliance achieved1 linked violation
October 18, 2011State Compliance achieved1 linked violation
October 18, 2011State Compliance achieved6 linked violations
October 18, 2011State Compliance achieved1 linked violation
October 18, 2011State Compliance achieved1 linked violation
October 18, 2011State Compliance achieved1 linked violation
October 18, 2011State Compliance achieved1 linked violation
October 6, 2011State Formal Notice of Violation issued1 linked violation
October 6, 2011State Public Notification requested1 linked violation
July 12, 2011State Public Notification received1 linked violation
June 21, 2011State Public Notification requested1 linked violation
June 21, 2011State Public Notification requested1 linked violation
June 21, 2011State Formal Notice of Violation issued1 linked violation
June 21, 2011State Formal Notice of Violation issued1 linked violation
April 19, 2011State Public Notification received4 linked violations
April 8, 2011State Public Notification requested1 linked violation
April 8, 2011State Public Notification requested1 linked violation
April 8, 2011State Formal Notice of Violation issued1 linked violation
April 8, 2011State Formal Notice of Violation issued1 linked violation
March 22, 2011State Public Notification requested1 linked violation
March 22, 2011State Formal Notice of Violation issued1 linked violation
March 22, 2011State Formal Notice of Violation issued3 linked violations
July 27, 2006State Public Notification requested6 linked violations
July 27, 2006State Formal Notice of Violation issued7 linked violations

Common questions

Is CRICKET HILL APARTMENTS required to publish a Consumer Confidence Report?: Yes. CRICKET HILL APARTMENTS 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 CRICKET HILL APARTMENTS’s next Consumer Confidence Report due?: CRICKET HILL APARTMENTS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CRICKET HILL APARTMENTS have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for CRICKET HILL APARTMENTS.
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

SPENCE, CONNIE M.

804-725-9214

MATHEWS, VA 23109