CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 2167980· CARRIER· EIN 26115386
⬇ PDF report

XINERGY CORP

8351 EAST WALKER SPRINGS ROAD SUITE #400, KNOXVILLE, TN, 37923(865) 474-7000lreynolds@xinergy.corp.comLARRY REYNOLDS
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
3
on file (MCS-150)
Drivers
3
1 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
  • Intrastate · <100 mi2 drivers
Company officer
LARRY REYNOLDS
Operation
Interstate
Registered since
2011-06-28
Last MCS-150 update
2011-06-28
Census status
I

Fleet: 3 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 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: BEE SURE TRANSPORT INC (USDOT 531502, registered 1993) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
1
930313 ONTARIO INC
USDOT 775092Active· PICTON, ON
Strong
Officer
2
BEE SURE TRANSPORT INC
USDOT 531502Inactive· ATWATER, MN
Strong
Officer
3
KIAMICHI WILDERNESS LANDOWNERS ASSOCIATION INC
USDOT 2578806Active· MOYERS, OK
Strong
Officer
4
LARRY D REYNOLDS
USDOT 2311442Inactive· BROWNS MILLS, NJ
Strong
Officer
5
LARRY H REYNOLDS
USDOT 248373Active· PIPESTONE, MN
Strong
Officer
6
LMR DRILLING LLC
USDOT 2569179Active· DOTHAN, AL
Strong
Officer
7
LTRAIN EXPRESS DELIVERY SERVICES LLC
USDOT 3967261Inactive· PERRYSBURG, OH
Strong
Officer
8
REYNOLDS ELECTRIC
USDOT 2782529Inactive· KANSAS CITY, MO
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. 06/28/2011Registered with FMCSA

    PRIVATE PROPERTY

  2. 06/28/2011MCS-150 update filed

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
2011-06-28
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 25, 2026, 1:44 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.