CSA
UnknownUSDOT 2766712· CARRIER
⬇ PDF report

MARIO A RODRIGUEZ

4013 E FOLSOM ST, LOS ANGELES, CA, 90063(323) 239-5466MARIO A RODRIGUEZ
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

AUTHORIZED FOR HIRE

Power units
1
on file (MCS-150)
Drivers
1
0 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
Company officer
MARIO A RODRIGUEZ
Operation
Intrastate (Non-Hazmat)
Registered since
2015-07-01
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 18 other carriers — review the connections below as part of your vetting.

18
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
18
Strong links
Possible reincarnation pattern: MARIO A RODRIGUEZ (USDOT 1089941, registered 2003) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 18
1
HIGHLAND TREE SERVICES INC
USDOT 3161031Active· KIRKLAND, WA
Strong
Officer
2
MAR CONTRACTOR INC
USDOT 2607191Active· ANTIOCH, CA
Strong
Officer
3
MARIO A RODRIGUEZ
USDOT 2730749Active· OAKLAND, CA
Strong
Officer
4
MARIO A RODRIGUEZ
USDOT 2731269Active· SYLMAR, CA
Strong
Officer
5
MARIO A RODRIGUEZ
USDOT 2732464Active· LONG BEACH, CA
Strong
Officer
6
MARIO A RODRIGUEZ
USDOT 2743831Active· SUN VALLEY, CA
Strong
Officer
7
MARIO A RODRIGUEZ
USDOT 4396277Active· OXNARD, CA
Strong
Officer
8
MARIO A RODRIGUEZ
USDOT 1089941Inactive· ALBUQUERQUE, NM
Strong
Officer
9
MARIO A RODRIGUEZ
USDOT 2781721Active· LANCASTER, TX
Strong
Officer
10
MARIO A RODRIGUEZ
USDOT 2044471Inactive· CYPRESS, TX
Strong
Officer
11
MARIO A RODRIGUEZ
USDOT 2053713Inactive· SAN ANTONIO, TX
Strong
Officer
12
MARIO A RODRIGUEZ
USDOT 2275972Active· HOUSTON, TX
Strong
Officer
13
MARIO RODRIGUEZ
USDOT 2879662Inactive· LANCASTER, CA
Strong
Officer
14
MARIO'S TRUCKING LLC
USDOT 2724261Inactive· LAREDO, TX
Strong
Officer
15
MARIOS TRUCKING LLC
USDOT 2771100Active· LOS ANGELES, CA
Strong
Officer
16
PRIMETIME FREIGHT SERVICES INC
USDOT 1198215Inactive· LAREDO, TX
Strong
Officer
17
TRANS MEX INTERNACIONAL
USDOT 219345Inactive· TIJUANA, BN
Strong
Officer
18
VALPARAISO EXPRESS LLC
USDOT 1504990Inactive· CENTER POINT, TX
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.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
0
⚡

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