Is RIO EN MEDIO MDWCA required to publish a Consumer Confidence Report?

Yes. RIO EN MEDIO MDWCA 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 RIO EN MEDIO MDWCA’s next Consumer Confidence Report due?

RIO EN MEDIO MDWCA’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.

TESUQUE, NM · Santa Fe County

RIO EN MEDIO MDWCA Water System

Consumer Confidence Report status

RIO EN MEDIO MDWCA 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 RIO EN MEDIO MDWCA.

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

System facts

System ID (PWSID): NM3533426
System type: Community Water System
Population served: 130
Service connections: 53
Ownership: local government
Water source: groundwater (wells)

RIO EN MEDIO MDWCA is one of 667 community water systems in New Mexico in the 500 or fewer people size category, serving 130 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

March 24, 2026State Compliance achieved1 linked violation
March 24, 2026State Compliance achieved1 linked violation
March 5, 2026State Public Notification received1 linked violation
March 5, 2026State Public Notification received1 linked violation
February 9, 2026State Violation/Reminder Notice7 linked violations
July 11, 2025State Violation/Reminder Notice1 linked violation
July 11, 2025State Violation/Reminder Notice1 linked violation
July 11, 2025State Public Notification requested1 linked violation
July 11, 2025State Public Notification requested1 linked violation
January 12, 2025State Violation/Reminder Notice2 linked violations
May 17, 2022State Compliance achieved1 linked violation
May 17, 2022State Public Notification received1 linked violation
October 30, 2020State Compliance achieved1 linked violation
October 30, 2020State Public Notification received1 linked violation
October 1, 2020State Compliance achieved1 linked violation
August 26, 2020State Compliance achieved1 linked violation
July 17, 2020State Violation/Reminder Notice1 linked violation
December 23, 2019State Violation/Reminder Notice1 linked violation
December 23, 2019State Public Notification requested1 linked violation
October 9, 2019State Compliance achieved1 linked violation
October 8, 2019State Violation/Reminder Notice1 linked violation
June 9, 2019State Compliance achieved1 linked violation
June 9, 2019State Compliance achieved1 linked violation
May 26, 2019State Compliance achieved2 linked violations
May 26, 2019State Compliance achieved1 linked violation
April 5, 2019State Compliance achieved1 linked violation
April 5, 2019State Compliance achieved1 linked violation
April 5, 2019State Public Notification received1 linked violation
April 5, 2019State Compliance achieved1 linked violation
April 5, 2019State Public Notification received8 linked violations
April 5, 2019State Compliance achieved1 linked violation
April 3, 2019State Compliance achieved1 linked violation
April 3, 2019State Compliance achieved1 linked violation
April 3, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved6 linked violations
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
March 28, 2019State Compliance achieved1 linked violation
January 18, 2019State Compliance achieved1 linked violation
January 15, 2019State Compliance achieved1 linked violation
January 3, 2019State Compliance achieved8 linked violations
January 3, 2019State Compliance achieved2 linked violations
February 6, 2018State Public Notification requested8 linked violations
October 25, 2017State Public Notification requested1 linked violation
October 25, 2017State Violation/Reminder Notice1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
October 5, 2017State Compliance achieved1 linked violation
September 14, 2017State Compliance achieved1 linked violation
July 21, 2017State Public Notification requested1 linked violation
July 21, 2017State Public Notification requested1 linked violation
July 21, 2017State Violation/Reminder Notice1 linked violation
July 21, 2017State Violation/Reminder Notice2 linked violations
July 21, 2017State Violation/Reminder Notice1 linked violation
March 22, 2017State Public Notification requested2 linked violations
March 22, 2017State Public Notification requested2 linked violations
October 17, 2016State Public Notification requested2 linked violations
October 17, 2016State Public Notification requested2 linked violations
October 17, 2016State Public Notification requested2 linked violations
October 13, 2016State Public Notification requested2 linked violations
September 8, 2016State Compliance achieved1 linked violation
July 29, 2016State Violation/Reminder Notice2 linked violations
February 8, 2016State Compliance achieved1 linked violation
February 8, 2016State Compliance achieved3 linked violations
October 1, 2015State Violation/Reminder Notice1 linked violation
January 20, 2015State Public Notification requested2 linked violations
December 1, 2014State Violation/Reminder Notice2 linked violations
September 15, 2012State Administrative/Compliance Order without penalty issued2 linked violations
September 14, 2012State Compliance achieved2 linked violations
September 13, 2012State Compliance achieved2 linked violations
September 11, 2012State Compliance achieved2 linked violations
November 18, 2011State Violation/Reminder Notice2 linked violations
November 18, 2011State Violation/Reminder Notice3 linked violations
August 1, 2011State Violation/Reminder Notice2 linked violations
August 1, 2011State Public Notification requested1 linked violation
August 1, 2011State Compliance achieved2 linked violations
July 18, 2008State Compliance achieved2 linked violations
July 18, 2008State Compliance achieved3 linked violations
July 10, 2006State Violation/Reminder Notice3 linked violations

Common questions

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

KADLECEK, JOHN

505-988-2205

TESUQUE, NM 87574