CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 773322· CARRIER
⬇ PDF report

J J TRUCKING

Legal: JOHNNY MARTINEZ

612 S W 10TH, SEMINOLE, TX, 79360(432) 889-4232JOHNNY MARTINEZ
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
None
nothing flagged
100
/ 100

Risk factors

Low riskVioCodes score
No red flags in the public FMCSA record

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
1
on file (MCS-150)
Drivers
1
1 hold a CDL
Annual mileage
0.1M mi
reported 1997
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · 100+ mi1 drivers
Company officer
JOHNNY MARTINEZ
Operation
Intrastate (Non-Hazmat)
Registered since
1998-09-25
Last MCS-150 update
2010-02-16
Census status
Active

Fleet: 1 trucks · 1 owned tractors · 1 owned trailers.

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

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
12
Strong links
Strong· 12
1
A-JUAN TRANSPORTATION LLC
USDOT 3908180Active· BURNET, TX
Strong
Officer
2
AUTUMN'S SEAFOOD LLC
USDOT 1897686Active· KROTZ SPRINGS, LA
Strong
Officer
3
J AND S TRANSPORT INC
USDOT 1467563Active· PASCO, WA
Strong
Officer
4
JOHN RAYMOND MARTINEZ
USDOT 1214864Inactive· SEMINOLE, TX
Strong
Officer
5
JOHNNY E MARTINEZ
USDOT 1837620Inactive· HILLSBOROUGH, NJ
Strong
Officer
6
JOHNNY MARTINEZ
USDOT 1980348Inactive· EL PASO, TX
Strong
Officer
7
JOHNNY MARTINEZ
USDOT 2039971Active· FLUVANNA, TX
Strong
Officer
8
JOHNNY MARTINEZ TRUCKING INC
USDOT 1005905Active· PASCO, WA
Strong
Officer
9
MARTINEZ & SON'S DELIVERY SERVICE
USDOT 2955042Active· VISALIA, CA
Strong
Officer
10
MARTINEZ & SONS DELIVERY SERVICE LLC
USDOT 2714500Active· VISALIA, CA
Strong
Officer
11
SAN MIGUEL TRANSPORT INC
USDOT 1864961Active· IRVINGTON, NJ
Strong
Officer
12
TRINITY LOGISTICS LLC
USDOT 3628421Active· PASCO, WA
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/16/2010MCS-150 update filed

    0.1M mi reported (1997)

  2. 09/25/1998Registered with FMCSA

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

🚛

Operations

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2010-02-16
Reported mileage
100,000 mi (1997)
⚡

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 23, 2026, 6:55 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.