Radius Recycling
Active WDID 5F10I003367 Fresno, Fresno County Region 5F · Central Valley (Fresno)
At a glance
- Permit Evidence: SMARTS record
- Active Industrial
- Notice of Intent (WDID code I) · Permits and applications
- Location Evidence: facility-reported
- Fresno, Fresno County
- Region 5F · Central Valley (Fresno) · Location · Statewide map
- Receiving water
- No offste discharge Fresno MS4 goes to infiltration ponds (as reported by the facility)
- Evidence: not confirmed Details
- Identified receiving water on the 2026 303(d) list
- Not established
- Shown only when the reported receiving water is identified and corroborated.
- 2026 Integrated Report waters within 1.0 km Evidence: geographic proximity
- None
- Monitoring results Evidence: facility-reported
- None in the current exports
- Compliance and enforcement records Evidence: SMARTS record
- 1 inspection · 2 violation records · 2 enforcement actions
- Counts as published in SMARTS; not a compliance determination · Details
Each label shows where a statement comes from. How to read the labels.
Overview and location
Reported facility location HUC12 watershed Corroborated receiving water 2026 Integrated Report waterbodies nearby
Reported location Evidence: facility-reported
- Coordinates
- 36.70233, -119.7364
- Precision
- 4 decimal places
- Shared point
- No
- Matches application record
- same
Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.
- Facility address
- 2727 S Chestnut Ave, Fresno 93725
- Regional Water Board
- 5F — Central Valley (Fresno)
HUC12 watershed Evidence: spatial
- Central Canal HUC12 180300090504
The facility's reported location lies within this HUC12 watershed (spatial derivation); it is not a discharge location.
Permits and applications Evidence: SMARTS record
Current permit record
- Permit type
- Industrial
- Application type
- Notice of Intent (WDID code I)
- Status
- Active
- Operator
- Radius Recycling Inc
- Primary industry (SIC)
- 5093-Scrap and Waste Materials
- Application ID
- 195722
- NOI processed
- Apr 03, 1992
- Last certified
- Jan 23, 2025
- Facility size
- 20 Acres
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 195722 | Industrial | Active | Apr 03, 1992 | — | Jan 23, 2025 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- No offste discharge Fresno MS4 goes to infiltration ponds
- Discharges directly / indirectly
- N / Y (as answered in the permit application)
Evidence: not confirmed Not matchable to a single waterbody
Receiving-water text as reported by the discharger in SMARTS; no waterbody identification has been confirmed.
Impaired waters and TMDLs
Two kinds of information, kept apart: 2026 Integrated Report waterbodies near the reported location (geographic proximity only), and TMDL records that SMARTS lists for this facility. Neither establishes where the facility discharges; see Receiving water for the facility's own statement.
Nearby waterbodies Evidence: geographic proximity
Spatial proximity only; discharge pathway not established. Being near a waterbody does not mean the facility discharges to it.
No 2026 Integrated Report waterbody lies within the proximity threshold of the reported location.
SMARTS TMDL records Evidence: SMARTS-reported
No TMDL records for this facility in the SMARTS TMDL export.
Reported monitoring results Evidence: facility-reported
Numeric Action Level (NAL) screening is being independently validated and is not shown. Nothing on this page states whether a result exceeded a NAL.
No industrial monitoring results for this permit are in the current exports.
Compliance and enforcement records Evidence: SMARTS record
These are records as the State Water Board publishes them in SMARTS, with the source's own types and statuses. They are not a compliance determination or rating. A record listed here is not proof of a violation beyond what the source states, and the absence of records does not establish compliance.
| Record type | Records | As published | Dates | Retrieved | List |
|---|---|---|---|---|---|
| Violations | 2 | 2 Violation · 0 Potential (preliminary) · 0 Dismissed | Feb 20, 2003 – Nov 19, 2013 | Oct 21, 2026 | All violations |
| Enforcement actions | 2 | 2 issued · 0 draft · 0 withdrawn, rescinded or superseded | Apr 17, 2003 – Dec 11, 2013 | Oct 21, 2026 | All actions |
| Inspections | 1 | inspections, not findings | Nov 19, 2013 – Nov 19, 2013 | Oct 21, 2026 | All inspections |
| Annual reports | 11 | certified reports (contents not shown) | 2015 – 2025 | Oct 21, 2026 | All reports |
| Water-quality-based corrective action reports | 0 | reports, by parameter | — | Oct 21, 2026 |
Each record type is counted by its own SMARTS identifier. A violation and the enforcement action that cites it are two records in two lists; they are never added together.
Chronological record history (16 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Jul 07, 2026 | Annual reports | 1336049 | Annual report 2025 | — | |
| Jun 30, 2025 | Annual reports | 1294892 | Annual report 2024 | — | |
| Jul 12, 2024 | Annual reports | 1244013 | Annual report 2023 | — | |
| Jul 13, 2023 | Annual reports | 1190048 | Annual report 2022 | — | |
| Jul 06, 2022 | Annual reports | 1113481 | Annual report 2021 | — | |
| Jul 12, 2021 | Annual reports | 1069526 | Annual report 2020 | — | |
| Jul 13, 2020 | Annual reports | 986847 | Annual report 2019 | — | |
| Jul 22, 2019 | Annual reports | 954434 | Annual report 2018 | — | |
| Jul 16, 2018 | Annual reports | 939852 | Annual report 2017 | — | |
| Jul 14, 2017 | Annual reports | 879143 | Annual report 2016 | — | |
| Jul 21, 2016 | Annual reports | 844116 | Annual report 2015 | — | |
| Dec 11, 2013 | Enforcement actions | 414618 | SEL (Staff Enforcement Letter) | Historical | |
| Nov 19, 2013 | Inspections | 2020486 | B Type compliance | — | No Further Action |
| Nov 19, 2013 | Violations | 853242 | Deficient BMP Implementation | Violation | Inspection |
| Apr 17, 2003 | Enforcement actions | 244793 | NOV (Notice of Violation) | Historical | UNKNOWN |
| Feb 20, 2003 | Violations | 226962 | Deficient BMP Implementation | Violation | Inspection |
Sources and provenance
| Information | Source | Retrieved or published |
|---|---|---|
| Permit, location, receiving-water text | SMARTS Industrial Application Specific Data | Oct 20, 2026 |
| Permit history | SMARTS Storm Water Applications | Oct 20, 2026 |
| Monitoring results | SMARTS Industrial Parameter Data | Oct 20, 2026 |
| Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12) | USGS | 2026-10-22 |
| 2026 California Integrated Report, Appendix A: 2026 303(d) List (final) | SWRCB | 2026-10-22 |
| Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0) | SWRCB GIS | 2026-10-22 |
| SMARTS TMDL requirements | SMARTS | 2026-10-21 |
Relationships computed 2026-10-22 with methods facility_huc12/1, proximity/1, receiving_water/2, tmdl_reference/1, waterbody_huc12_ovl/1, waterbody_huc12_pub/1; proximity threshold 1.0 km.
How to read the evidence labels
- Evidence: SMARTS record Evidence: facility-reported Information as published in SMARTS or reported by the discharger.
- Evidence: identification corroborated The reported receiving-water name identifies one official waterbody and the facility's location is consistent with it. It does not establish a discharge pathway.
- Evidence: candidate, awaiting review Evidence: not confirmed The reported name could match one or more official waterbodies, but no identification has been confirmed; nothing is assigned without review.
- Evidence: spatial Evidence: geographic proximity Derived from the reported location only.
- Evidence: SMARTS-reported Source records whose links to official references are not yet reviewed.
- Evidence: unavailable The information could not be loaded or is not in the sources.
Records are shown as published and are not compliance determinations. How geographic context is derived.