CSA
UnknownUSDOT 1325307· CARRIER· EIN 31-1757304
⬇ PDF report

JORGE L PEREZ

6580 W FLAGLER ST APT 304, MIAMI, FL, 33144(786) 208-5541JORGE L 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
Power units
0
on file (MCS-150)
Drivers
—
Annual mileage
—
Recordable crash rate
—
per million miles
Company officer
JORGE L PEREZ
Registered since
2005-01-25
Last MCS-150 update
2011-02-17
Census status
I

Fleet: 0 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: JMP TRANSPORT INC (USDOT 1240018, registered 2004) 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
JM&JM UNLIMITED TRANSPORT INC
USDOT 3041608Active· MIAMI, FL
Strong
Officer
2
JMP TRANSPORT INC
USDOT 1240018Inactive· MIAMI, FL
Strong
Officer
3
JORGE C PEREZ
USDOT 970509Inactive· DEMOPOLIS, AL
Strong
Officer
4
JORGE L LOPEZ
USDOT 1340128Active· MIAMI, FL
Strong
Officer
5
JORGE L PEREZ
USDOT 1702646Active· LIBERAL, KS
Strong
Officer
6
JORGE L PEREZ
USDOT 2848680Active· AGUA DULCE, CA
Strong
Officer
7
JORGE L PEREZ
USDOT 2726990Inactive· MIAMI, FL
Strong
Officer
8
JORGE L PEREZ
USDOT 2730898Active· OXNARD, CA
Strong
Officer
9
JORGE L PEREZ
USDOT 2758998Inactive· BLOOMINGTON, CA
Strong
Officer
10
JORGE L PEREZ
USDOT 2765995Active· SAN DIEGO, CA
Strong
Officer
11
JORGE L PEREZ
USDOT 1245271Active· ORLANDO, FL
Strong
Officer
12
JORGE L PEREZ
USDOT 2311640Inactive· MIAMI, FL
Strong
Officer
13
JT SERVICES SOLUTIONS LLC
USDOT 4540827Active· TAMPA, FL
Strong
Officer
14
MILLENIUM XXI TRANSPORT INC
USDOT 1446218Inactive· DORAL, FL
Strong
Officer
15
NASA LOGISTICS LLC
USDOT 2099061Inactive· ALTAMONTE SPRINGS, FL
Strong
Officer
16
NEXT LEVEL CONCRETE TRANSPORT, INC.
USDOT 2746078Active· PARAMOUNT, CA
Strong
Officer
17
RED ROOSTER TRUCKING LLC
USDOT 2060854Active· NORTH BERGEN, NJ
Strong
Officer
18
SIMONEAU TRUCKING LLC
USDOT 1281750Inactive· TAMPA, FL
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. 02/17/2011MCS-150 update filed
  2. 01/25/2005Registered with FMCSA

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

★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2011-02-17
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 26, 2026, 9:45 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.