CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 3201009· CARRIER· EIN 83-2190763
⬇ PDF report

YIREH LOGISTICS INC

18946 VICKIE APT 259, CERRITOS, CA, 90703(951) 692-0735yirehlogistics18@outlook.comPEDRO DAVILA
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
1 hold a CDL
Annual mileage
0M mi
reported 2022
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi1 drivers
Company officer
PEDRO DAVILA
Operation
Intrastate (Non-Hazmat)
Registered since
2018-10-16
Last MCS-150 update
2023-03-24
Census status
I

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 phone numbers or officers with 12 other carriers — review the connections below as part of your vetting.

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
11
Strong links
Possible reincarnation pattern: DAVILA TRANSPORT (USDOT 2029172, registered 2010) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 11
1
ALISSON TRUCKING INC
USDOT 3534013Inactive· PROVIDENCE, RI
Strong
Officer
2
DAVILA CORPORATION
USDOT 948720Active· ANCHORAGE, AK
Strong
Officer
3
DAVILA TRANSPORT
USDOT 2029172Inactive· GURABO, PR
Strong
Officer
4
DAVILA TRUCKING SERVICE INC
USDOT 2778308Inactive· WEST PALM BEACH, FL
Strong
Officer
5
PAA TRANSPORT LLC
USDOT 4036843Active· SIGNAL HILL, CA
Strong
Officer
6
PEDRO DAVID DAVILA
USDOT 3535774Inactive· LAKIN, KS
Strong
Officer
7
PEDRO DAVILA
USDOT 2941503Inactive· FONTANA, CA
Strong
Officer
8
PEDRO DAVILA
USDOT 2740257Active· LOS ANGELES, CA
Strong
Officer
9
PEDRO DAVILA
USDOT 1052380Active· LOXAHATCHEE, FL
Strong
Officer
10
PEDRO DAVILA
USDOT 1722361Inactive· SPARKS, NV
Strong
Officer
11
SHEILA TRUCKING LLC
USDOT 3396350Inactive· LOUISVILLE, KY
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. 03/24/2023MCS-150 update filed

    0.0M mi reported (2022)

  2. 10/16/2018Registered with FMCSA

    AUTHORIZED FOR HIRE

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
2023-03-24
Reported mileage
2,785 mi (2022)
⚡

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