CSA
UnknownUSDOT 4531822· CARRIER· EIN 39-3218947
⬇ PDF report

MUYRIDELLC

3420 W BELMONT AVE, PHOENIX, AZ, 85051-6541(602) 748-3300muyride@yahoo.comJESUS JUAREZ
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
80
/ 100

Risk factors

Low riskVioCodes score
Possible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

AUTHORIZED FOR HIRE

Power units
1
on file (MCS-150)
Drivers
2
1 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · 100+ mi1 drivers
  • Intrastate · <100 mi1 drivers
Company officer
JESUS JUAREZ
Operation
Intrastate (Non-Hazmat)
Registered since
2026-02-10
Last MCS-150 update
2026-02-10
Census status
Active

Fleet: 1 trucks · 1 owned tractors.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

This carrier shares officers with 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: J JUAREZ PRODUCE INC (USDOT 1903098, registered 2009) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
1
ALL ROADS FREIGHT LLC
USDOT 4237863Active· LAREDO, TX
Strong
Officer
2
AMERICAN LANDSCAPING AND DESIGN INC
USDOT 2494124Active· TEMPLE HILLS, MD
Strong
Officer
3
J JUAREZ PRODUCE INC
USDOT 1903098Inactive· OXNARD, CA
Strong
Officer
4
J JUAREZ PRODUCE INC
USDOT 2360226Active· OXNARD, CA
Strong
Officer
5
JESUS EDUARDO JUAREZ
USDOT 3380337Inactive· LABELLE, FL
Strong
Officer
6
JESUS JUAREZ
USDOT 1320210Inactive· COACHELLA, CA
Strong
Officer
7
JESUS JUAREZ
USDOT 1598489Active· RIVERDALE, MD
Strong
Officer
8
JUAREZ FARMING LLC
USDOT 2255730Active· LABELLE, FL
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

2 events
  1. 02/10/2026Registered with FMCSA

    AUTHORIZED FOR HIRE

  2. 02/10/2026MCS-150 update filed

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2026-02-10
Reported mileage
—
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 28, 2026, 5:58 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.