CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 4526895· CARRIER· EIN 41-3875250
⬇ PDF report

FRANKLIN J TRUCKING LLC

5700 NETHERFIELD CT APT 203, FREDERICKSBURG, VA, 22407-6799(571) 552-7693franklinjoelog@gmail.comFRANKLIN RODRIGUEZ
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

AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

Power units
2
on file (MCS-150)
Drivers
1
1 hold a CDL
Annual mileage
0M mi
reported 2025
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
Company officer
FRANKLIN RODRIGUEZ
Operation
Interstate
Registered since
2026-01-31
Last MCS-150 update
2026-06-15
Census status
Active

Fleet: 1 trucks · 1 owned tractors.

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 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: DTOF COMPANY INC (USDOT 2029033, registered 2010) 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
DTOF COMPANY INC
USDOT 2029033Inactive· LEHIGH ACRES, FL
Strong
Officer
2
FKK RODRIGUEZ LLC
USDOT 4257627Active· SPRINGFIELD, MA
Strong
Officer
3
FRANKLIN RODRIGUEZ
USDOT 1585740Inactive· SPRINGFIELD, MA
Strong
Officer
4
FRANKLIN RODRIGUEZ
USDOT 3671118Active· PEEKSKILL, NY
Strong
Officer
5
FRANKLIN RODRIGUEZ
USDOT 2073585Inactive· BROOKLYN, NY
Strong
Officer
6
L & B TRANSPORTATION CORPORATION
USDOT 3339399Inactive· PERTH AMBOY, NJ
Strong
Officer
7
ROARI LLC
USDOT 2969832Active· TEMPLE HILLS, MD
Strong
Officer
8
SECOND2NONE TRANSPORT LLC
USDOT 4202251Active· CHARLOTTE, NC
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

4 events
  1. 09/25/2026Out-of-service order rescinded
  2. 06/15/2026MCS-150 update filed

    0.0M mi reported (2025)

  3. 04/28/2026Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  4. 01/31/2026Registered with FMCSA

    AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

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

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2026-06-15
Reported mileage
1 mi (2025)
⚡

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