CSA
UnknownUSDOT 7966758· CARRIER
⬇ PDF report

A J PEREZ

BO QUEMADO CARR 181 KM 2.2, SAN LORENZO, PR, 00754(787) 510-0933ALEXJAVIER959@GMAIL.COMALEX PEREZ
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
2
on file (MCS-150)
Drivers
4
1 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi1 drivers
  • Interstate · <100 mi1 drivers
  • Intrastate · 100+ mi1 drivers
  • Intrastate · <100 mi1 drivers
Company officer
ALEX PEREZ
Operation
Intrastate (Non-Hazmat)
D-U-N-S
599542649
Registered since
2026-09-25
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 16 other carriers — review the connections below as part of your vetting.

16
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
16
Strong links
Possible reincarnation pattern: ADE TRUCKING (USDOT 3657666, registered 2021) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 16
1
ADE TRUCKING
USDOT 3657666Inactive· MONTCLAIR, NJ
Strong
Officer
2
ANY STATE TRANSPORT LLC
USDOT 2638640Inactive· HIALEAH, FL
Strong
Officer
3
AROCEANO EXPRESS LLC
USDOT 3205483Active· MIAMI, FL
Strong
Officer
4
AROCEANO INC
USDOT 3115951Active· MIAMI, FL
Strong
Officer
5
ASHLEY & EMILY TRUCKING LLC
USDOT 3283531Active· HOBOKEN, NJ
Strong
Officer
6
ASHLEY TRUCKING CORP
USDOT 2258972Active· HOBOKEN, NJ
Strong
Officer
7
CALMEX LOGISTICS LLC
USDOT 3005870Inactive· FONTANA, CA
Strong
Officer
8
CIRCLE CITY MOTORS INC
USDOT 2768576Active· ANAHEIM, CA
Strong
Officer
9
COLGARDEN GROUP INC
USDOT 4152245Active· ASTORIA, NY
Strong
Officer
10
DSAP TRANSPORTATION LLC
USDOT 3684430Active· ATLANTA, GA
Strong
Officer
11
DSAP TRANSPORTATION LLC
USDOT 3684455Inactive· ATLANTA, GA
Strong
Officer
12
M&A FAST TRANSPORT LLC
USDOT 3088343Active· KISSIMMEE, FL
Strong
Officer
13
NATIONAL EXPRESS TRUCKING LLC
USDOT 4025680Inactive· RICHMOND, VA
Strong
Officer
14
PEREZ AUTOEXPRESS LLC
USDOT 3605549Active· MIAMI, FL
Strong
Officer
15
TITAN FREIGHT GROUP INC
USDOT 3479386Active· CHINO HILLS, CA
Strong
Officer
16
ZENKIS TRANSPORT LLC
USDOT 4269614Active· MILWAUKEE, WI
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

  • PRIVATE PROPERTY

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