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

VICTOR M MARTINEZ

853 S BUCKLEY AVE, TYLER, TX, 75701(903) 372-2444vmm196354@gmail.comVICTOR M 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

AUTHORIZED FOR HIRE

Power units
1
on file (MCS-150)
Drivers
1
1 hold a CDL
Annual mileage
0.8M mi
reported 2023
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi1 drivers
Company officer
VICTOR M MARTINEZ
Operation
Intrastate (Non-Hazmat)
Registered since
2015-06-01
Last MCS-150 update
2023-08-31
Census status
Active

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.

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

10
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
10
Strong links
Strong· 10
1
A-MEX,INC.
USDOT 2745235Active· VERNON, CA
Strong
Officer
2
ALTA FINISH & STAIR INC
USDOT 3357673Active· MORENO VALLEY, CA
Strong
Officer
3
K V TRUCKING LLC
USDOT 2674773Active· SAN FRANCISCO, CA
Strong
Officer
4
M&M QUEEN LLC
USDOT 3669615Inactive· AUSTIN, TX
Strong
Officer
5
MARTINEZ RECYCLING INC
USDOT 2751566Active· HUNTINGTON PARK, CA
Strong
Officer
6
ORANGE STATION TRANSPORT INC
USDOT 3322490Active· JURUPA VALLEY, CA
Strong
Officer
7
VICTOR M MARTINEZ
USDOT 2809268Active· CAPITOLA, CA
Strong
Officer
8
VICTOR M MARTINEZ
USDOT 2758487Active· FULLERTON, CA
Strong
Officer
9
VICTOR M MARTINEZ
USDOT 1949169Active· DALLAS, TX
Strong
Officer
10
VIX TRUCKING LLC
USDOT 3614115Active· MILWAUKEE, WI
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. 08/31/2023MCS-150 update filed

    0.8M mi reported (2023)

  2. 06/01/2015Registered with FMCSA

    AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2023-08-31
Reported mileage
838,950 mi (2023)
⚡

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