CSA
UnknownUSDOT 1658482· CARRIER
⬇ PDF report

ANGEL MUNOZ DE JESUS

117 HAROLD STREET, PROVIDENCE, RI, 02909(401) 867-0023alan25munoz@gmail.comANGEL MUNOZ
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%

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
1
0 hold a CDL
Annual mileage
0.1M mi
reported 2025
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
Company officer
ANGEL MUNOZ
Operation
Interstate · Hazmat
Registered since
2007-06-21
Last MCS-150 update
2026-02-17
Census status
Active

Fleet: 1 trucks.

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 10 other carriers — review the connections below as part of your vetting.

10
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
10
Strong links
Possible reincarnation pattern: ANGEL MUNOZ (USDOT 1337034, registered 2005) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 10
1
2M TRUCKING LLC
USDOT 3220263Active· LAMAR, CO
Strong
Officer
2
A & M OILFIELD SERVICES LLC
USDOT 4288722Active· CARLSBAD, NM
Strong
Officer
3
AGL TRANSPORT SERVICES LLC
USDOT 4366534Active· LIVE OAK, FL
Strong
Officer
4
ANGEL MUNOZ
USDOT 1337034Inactive· CICERO, IL
Strong
Officer
5
ANGEL MUNOZ
USDOT 2656223Active· RICHGROVE, CA
Strong
Officer
6
ANGEL MUNOZ
USDOT 2353488Active· LAKE CITY, FL
Strong
Officer
7
D & R TRANSPORTATION INC
USDOT 1568154Inactive· LOS ANGELES, CA
Strong
Officer
8
J J A MUNOZ DIST INC
USDOT 820957Active· EL PASO, TX
Strong
Officer
9
MUNOZ TRANSPORTING LLC
USDOT 3218422Inactive· SANTAQUIN, UT
Strong
Officer
10
TMUNOZ TRUCKING CORP
USDOT 3903456Inactive· HAZLE TOWNSHP, PA
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

4 events
  1. 02/17/2026MCS-150 update filed

    0.1M mi reported (2025)

  2. 04/03/2013Out-of-service order rescinded
  3. 12/23/2008Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  4. 06/21/2007Registered with FMCSA

    PRIVATE PROPERTY

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2026-02-17
Reported mileage
133,569 mi (2025)
📜

Changes on file

FMCSA census history
  1. January, 2021

    First on-record entry — ANGEL MUNOZ, ,

⚡

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 26, 2026, 5:40 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.