Public water system record

WILLIAM FISHER MEMORIAL WATER COMPANY

Federal records show 37 health-based violations and 1 monitoring/reporting issue for WILLIAM FISHER MEMORIAL WATER COMPANY in the last ten years. The most serious issue in this window was a resolved Fluoride violation.

  • CA1500455
  • MOJAVE
  • CA
  • 56 served

System profile

Source water Groundwater
ZIP 93501
Acute record in 10 years No

Verify this system on EPA ECHO →

Health-based records
37
Last 10 years
Monitoring issues
1
Last 10 years
Resolved vs. unresolved
38 resolved • 0 unresolved
PWSID
CA1500455
EPA public water system identifier

Check your address

Check whether your address is served by this system.

Use the normal Tap Truth address lookup to verify whether a specific home resolves to WILLIAM FISHER MEMORIAL WATER COMPANY.

Runs the same address-to-system lookup used on the homepage. Address suggestions by Mapbox

Health-based violations

Violation data reflects EPA records through December 2024. For the most current status, visit the EPA ECHO database.

Contaminant Rule family Start date Status Acute
Fluoride
Contaminant limit exceeded
330 Apr 1, 2025 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2025 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2024 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2024 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2024 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2024 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2023 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2023 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2023 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2023 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2022 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2022 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2022 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2022 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2021 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2021 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2021 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2021 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2020 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2020 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2020 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2019 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2019 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2019 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2019 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2018 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2018 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2018 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2018 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2017 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2017 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2017 Resolved No
Fluoride
Contaminant limit exceeded
330 Jan 1, 2017 Resolved No
Fluoride
Contaminant limit exceeded
330 Oct 1, 2016 Resolved No
Fluoride
Contaminant limit exceeded
330 Jul 1, 2016 Resolved No
Fluoride
Contaminant limit exceeded
330 Apr 1, 2016 Resolved No

Monitoring and reporting issues

Monitoring violations are administrative records. They mean required testing or reporting was missed, not that a contaminant was found above a safe level.

Issue Start date Status
Fluoride
Monitoring and reporting
Apr 1, 2019 Resolved