CSA
UnknownUSDOT 1621370· CARRIER
⬇ PDF report

VICTOR THOMAS

3110 LEZELLE ST LOT 400, STURGIS, SD, 57785(605) 347-6315tom@spe.midco.netVICTOR THOMAS
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

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
1
1 hold a CDL
Annual mileage
0M mi
reported 2006
Recordable crash rate
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi1 drivers
Company officer
VICTOR THOMAS
Operation
Interstate
Registered since
2007-03-21
Last MCS-150 update
2007-03-21
Census status
I

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.

Connections

carrier graph

This carrier shares officers with 9 other carriers — review the connections below as part of your vetting.

9
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
9
Strong links
Possible reincarnation pattern: VICTOR THOMAS (USDOT 1095701, registered 2003) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 9
1
AMERICAN FAST FREIGHT INC
USDOT 340754Active· FIFE, WA
Strong
Officer
2
BSR LOGISTICS LLC
USDOT 4228285Active· NUTLEY, NJ
Strong
Officer
3
ODYSSEY TRANSPORT & WAREHOUSE LLC
USDOT 213341Active· CHESTERTON, IN
Strong
Officer
4
RETIREMENT TRANSPORTATION LLC
USDOT 3317483Inactive· GIBSONVILLE, NC
Strong
Officer
5
RPM HARBOR SERVICES INC
USDOT 925567Active· FULLERTON, CA
Strong
Officer
6
T2 TRUCKING LLC
USDOT 1952131Active· BRYAN, TX
Strong
Officer
7
THOMAS & SONS AUTO TRANSPORTING LLC
USDOT 1770091Inactive· DOUGLASVILLE, GA
Strong
Officer
8
VICTOR T SANCHEZ
USDOT 1956511Active· HOUSTON, TX
Strong
Officer
9
VICTOR THOMAS
USDOT 1095701Inactive· GEORGETOWN, DE
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

3 events
  1. 10/26/2007Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  2. 03/21/2007Registered with FMCSA

    PRIVATE PROPERTY

  3. 03/21/2007MCS-150 update filed

    0.0M mi reported (2006)

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
📄

MCS-150 registration

Form date
2007-03-21
Reported mileage
10,000 mi (2006)

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