VioCodes logo
SearchMapNewCarriers
Lookup2
InsightsCalculatorDaily LogToolkit
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
Authorized · PropertyUSDOT 842948· MX372319· CARRIER
⬇ PDF report

TRANSPORTES VIRAMONTES

Legal: HUGO VIRAMONTES VALENZUELA

MIGUEL BRAVO 1859, MEXICALI, BN, 21379(686) 906-7583hugo.viramontes@transportesviramontes.comHUGO VIRAMONTES
Vetting snapshot
Authority
Active
operating authority
Insurance
No active filing
$750K required — verify
Vehicle OOS
7.1%
below 22% national avg
Driver OOS
0.3%
below 6.7% national avg
Crashes 24mo
0
clean
Red flags
1 flag
see details below
55
/ 100

Risk factors

Moderate riskVioCodes score
No 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

MX372319

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

No active liability (BIPD) insurance filing on file
Common
Active
Contract
Inactive
Broker
None
Authorized for: Property, Private
Liability (BIPD)
No active filing
$750K required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (3) ▾
05/27/2003FOR HIRE PROPERTYGRANTED
03/09/2000FOR HIRE HOUSEHOLD GOODSGRANTED→ REPLACED BY PROVISIONAL AUTHORITY (05/21/2003)
03/09/2000PRIVATE CARRIERGRANTED→ REPLACED BY PROVISIONAL AUTHORITY (05/21/2003)

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.

Vehicle239 inspections · 7.1% OOS · National 22%
Driver379 inspections · 0.3% OOS · National 6.7%

Company profile

FMCSA census

PRIVATE PROPERTY;AUTHORIZED FOR HIRE

Power units
23
on file (MCS-150)
Drivers
23
23 hold a CDL
Annual mileage
0.1M mi
reported 2023
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi23 drivers
Company officer
HUGO VIRAMONTES
Operation
Interstate
Registered since
1999-12-07
Last MCS-150 update
2024-09-04
Census status
Active

Fleet: 23 trucks · 7 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.

Activity history

5 events
  1. 09/04/2024MCS-150 update filed

    0.1M mi reported (2023)

  2. 05/27/2003FOR HIRE PROPERTY — GRANTED
  3. 03/09/2000FOR HIRE HOUSEHOLD GOODS — GRANTED

    REPLACED BY PROVISIONAL AUTHORITY (05/21/2003)

  4. 03/09/2000PRIVATE CARRIER — GRANTED

    REPLACED BY PROVISIONAL AUTHORITY (05/21/2003)

  5. 12/07/1999Registered with FMCSA

    PRIVATE PROPERTY;AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

  • PRIVATE PROPERTY;AUTHORIZED FOR HIRE

Area served

  • Interstate
★

FMCSA safety rating

Rating
Satisfactory
Type
Compliance review
Rated
2007-10-25
Last review
2007-10-23
📄

MCS-150 registration

Form date
2024-09-04
Reported mileage
88,649 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: Oct 2026 · Page refreshed: Nov 9, 2026, 10:05 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.