CSA
Not AuthorizedUSDOT 1993641· MC704759· CARRIER
⬇ PDF report

SALINAS TRUCKING

Legal: RUDY SALINAS

3327 SOUTH US HWY 83, ZAPATA, TX, 78076(956) 763-7347el_crazy_96@yahoo.comRUDY SALINAS
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
$750K required — verify
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
0
/ 100

Risk factors

High riskVioCodes score
Operating authority is not activeNo active liability (BIPD) insurance filing on file

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.

Authority & insurance

MC704759

Operating authority and insurance on file — from FMCSA Licensing & Insurance (L&I).

No active liability (BIPD) insurance filing on file
Common
None
Contract
None
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
$750K required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (1) ▾
03/23/2010MOTOR PROPERTY COMMON CARRIERDISMISSED

Source: FMCSA Licensing & Insurance (L&I), public data. This shows the carrier’s federal insurance filings (BMC-91X liability, BMC-34 cargo) — the federally-required minimums on file for operating authority — not the carrier’s full commercial policy (its actual auto combined-single-limit, general liability, cargo, or workers’ comp, which appear on the carrier’s ACORD certificate of insurance). Always confirm current coverage with a COI from the carrier’s agent before making a vetting decision.

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

Power units
1
on file (MCS-150)
Drivers
—
Annual mileage
0.1M mi
reported 2009
Recordable crash rate
—
per million miles
Company officer
RUDY SALINAS
Operation
Intrastate (Non-Hazmat)
Registered since
2010-02-10
Last MCS-150 update
2010-03-24
Census status
I

Fleet: 0 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 addresses or officers with 4 other carriers — review the connections below as part of your vetting.

4
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
3
Strong links
Strong· 3
1
RUDY SALINAS
USDOT 2060279Active· CEDAR CREEK, TX
Strong
Officer
2
RUDY'S CUSTOM CONCRETE LLC
USDOT 3045203Active· BRENTWOOD, CA
Strong
Officer
3
SALINAS EXPRESS LLC
USDOT 2509486Active· ZAPATA, TX
Strong
Officer
Medium· 1
RUBEN SALINAS SR
USDOT 2072706Active· ZAPATA, TX
Medium
Address

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. 03/24/2010MCS-150 update filed

    0.1M mi reported (2009)

  2. 03/23/2010MOTOR PROPERTY COMMON CARRIER — DISMISSED
  3. 02/10/2010Registered 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
2010-03-24
Reported mileage
72,800 mi (2009)
⚡

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