CSA
UnknownUSDOT 1607072· CARRIER· EIN 22-3432997
⬇ PDF report

LUIS A TORRES

245 SURREY PARK DR, FAYETTEVILLE, GA, 30215(678) 519-1729LUIS A TORRES
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%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census
Power units
0
on file (MCS-150)
Drivers
—
Annual mileage
—
Recordable crash rate
—
per million miles
Company officer
LUIS A TORRES
Registered since
2007-02-13
Last MCS-150 update
2010-10-01
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 13 other carriers — review the connections below as part of your vetting.

13
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
13
Strong links
Possible reincarnation pattern: M & S TRKG LOGISTICS (USDOT 1029489, registered 2002) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 13
1
A & J HAULING TRANSPORT LLC
USDOT 4146121Inactive· PENNSAUKEN, NJ
Strong
Officer
2
BRIDGET LLC
USDOT 4442130Active· ST CLOUD, FL
Strong
Officer
3
J&L TRUCKING SERVICE CORP
USDOT 3447374Active· MINE HILL, NJ
Strong
Officer
4
K & B TRUCKING LOGISTICS LLC
USDOT 662844Active· KISSIMME, FL
Strong
Officer
5
L & J TOWING INC
USDOT 2927145Active· CHICAGO, IL
Strong
Officer
6
LTMB LOGISTICS INC
USDOT 2456023Inactive· TAMPA, FL
Strong
Officer
7
LUIS A LA TORRE PEREZ
USDOT 4361433Active· LARES, PR
Strong
Officer
8
LUIS A TORRES
USDOT 1598687Inactive· PERRIS, CA
Strong
Officer
9
LUIS A TORRES
USDOT 2729946Active· LYNWOOD, CA
Strong
Officer
10
LUIS A TORRES
USDOT 1715286Inactive· KISSIMMEE, FL
Strong
Officer
11
LUIS A TORRES
USDOT 4272498Active· ARECIBO, PR
Strong
Officer
12
M & S TRKG LOGISTICS
USDOT 1029489Inactive· LINDEN, NJ
Strong
Officer
13
PIRO SOLUTIONS SERVICES LLC
USDOT 3766108Active· MIAMI, 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. 10/01/2010MCS-150 update filed
  2. 02/13/2007Registered 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
2010-10-01
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 27, 2026, 10:50 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.