CSA
UnknownUSDOT 3090177· CARRIER· EIN 82-3659070
⬇ PDF report

AGEMPLEO LP

262 W TEFFT ST, NIPOMO, CA, 93444-8882(805) 305-2623coinserve@gmail.comCARLOS CASTANEDA
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
3
on file (MCS-150)
Drivers
6
3 hold a CDL
Annual mileage
reported 0
Recordable crash rate
per million miles
How far they run · drivers by operating lane
  • Intrastate · 100+ mi3 drivers
  • Intrastate · <100 mi3 drivers
Company officer
CARLOS CASTANEDA
Operation
Intrastate (Non-Hazmat)
Registered since
2018-01-26
Last MCS-150 update
2018-01-26
Census status
Active

Fleet: 0 trucks · 3 buses.

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

Connections

carrier graph

This carrier shares addresses, phone numbers or officers with 14 other carriers — review the connections below as part of your vetting.

14
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
14
Strong links
Possible reincarnation pattern: CARLOS CASTANEDA (USDOT 1907447, 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· 14
1
CARLOS CASTANEDA
USDOT 2252580Active· CEDAR CREST, NM
Strong
Officer
2
CARLOS CASTANEDA
USDOT 2414760Active· KATY, TX
Strong
Officer
3
CARLOS CASTANEDA
USDOT 1907447Inactive· LAWRENCEVILLE, GA
Strong
Officer
4
CARLOS CASTANEDA
USDOT 876858Inactive· LATHROP, CA
Strong
Officer
5
CARLOS CASTANEDA
USDOT 3061966Inactive· FARMERSVILLE, TX
Strong
Officer
6
CARLOS COSTANEDA
USDOT 2954435Active· CHATTANOOGA, TN
Strong
Officer
7
CHARLIES SOIL SAMPLING DRILLING CORP
USDOT 3205012Active· SUN VALLEY, CA
Strong
Officer
8
CORAS GENERAL TRUCKING INC
USDOT 3647024Inactive· TONICA, IL
Strong
Officer
9
CORAS WELDING SHOP INC
USDOT 2348946Inactive· STREATOR, IL
Strong
Officer
10
DEKE TRUCKING SERVICES INC
USDOT 3875597Inactive· STREATOR, IL
Strong
Officer
11
FRESH LINK LOGISTICS LLC
USDOT 1004440Active· GARDENA, CA
Strong
Officer
12
LA ALIANZA LP
USDOT 3723849Active· NIPOMO, CA
Strong
OfficerMailingPhone
13
MASTERCRAFT ELECTRIC INC
USDOT 2323821Inactive· PACIFIC, WA
Strong
Officer
14
TRANSPORT BOYZ LLC
USDOT 3917477Active· SUN VALLEY, CA
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. 01/26/2018Registered with FMCSA

    PRIVATE PROPERTY

  2. 01/26/2018MCS-150 update filed

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Intrastate (Non-Hazmat)

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
📄

MCS-150 registration

Form date
2018-01-26
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 23, 2026, 3:18 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.