CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
Authorized · PropertyUSDOT 2595285· MC910843· CARRIER· EIN 26-4301387
⬇ PDF report

DULCES LA MOLIENDA CORP

2422 FREEDOM SUITE C, SAN ANTONIO, TX, 78217(210) 637-6825erik@dulceslamoliendausa.comROGELIO SALAZAR
Vetting snapshot
Authority
Active
operating authority
Insurance
$750K BIPD
VANTAPRO SPECIALTY INSURANCE COMPANY
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.

Authority & insurance

MC910843

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

Common
None
Contract
Active
Broker
None
Authorized for: Property
Liability (BIPD)
$750K on file
$750K required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Insurance filings
ON FILELiability (BIPD) — BMC-91X$750K coverageeff 09/11/2019
VANTAPRO SPECIALTY INSURANCE COMPANY· policy 5087-0153-01
Authority history (2) ▾
09/27/2018CONTRACTINVOLUNTARY REVOCATION→ DISCONTINUED REVOCATION (10/01/2018)
05/21/2015MOTOR PROPERTY CONTRACT CARRIERGRANTED
Insurance history2 insurers on record
Filing timeline (5) ▾
  1. VANTAPRO SPECIALTY INSURANCE COMPANY$1MCancelled
    BIPD/Primary · eff 09/11/2018 → 10/10/2019
  2. VANTAPRO SPECIALTY INSURANCE COMPANY$1MReplaced
    BIPD/Primary · eff 09/11/2018 → 09/11/2019
  3. PROGRESSIVE COUNTY MUTUAL$750KCancelled
    BIPD/Primary · eff 04/10/2015 → 10/24/2018
  4. PROGRESSIVE COUNTY MUTUAL$750KReplaced
    BIPD/Primary · eff 04/10/2015 → 09/11/2018
  5. PROGRESSIVE COUNTY MUTUAL$750KReplaced
    BIPD/Primary · eff 04/10/2015 → 04/10/2015

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
11
on file (MCS-150)
Drivers
11
0 hold a CDL
Annual mileage
0M mi
reported 2018
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi11 drivers
Company officer
ROGELIO SALAZAR
Operation
Interstate
Registered since
2015-04-01
Last MCS-150 update
2019-11-25
Census status
I

Fleet: 11 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 phone numbers or officers with 13 other carriers — review the connections below as part of your vetting.

13
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
10
Strong links
Strong· 10
1
ALAMO GLOBAL LOGISTICS LLC
USDOT 4042836Active· SAN ANTONIO, TX
Strong
Officer
2
ALAMO GLOBAL LOGISTICS LLC
USDOT 3638296Inactive· SAN ANTONIO, TX
Strong
Officer
3
BRS SALAZAR HAULING LLC
USDOT 4382303Active· EL CAMPO, TX
Strong
Officer
4
DIRECT TRANSPORTATION LLC
USDOT 3309884Active· HOUSTON, TX
Strong
Officer
5
DLM EXPRESS LLC
USDOT 3344972Inactive· SAN ANTONIO, TX
Strong
Officer
6
ROGELIO SALAZAR
USDOT 2665651Active· SANTA ANA, CA
Strong
Officer
7
ROGELIO SALAZAR
USDOT 1945049Active· DALLAS, TX
Strong
Officer
8
ROGELIO SALAZAR
USDOT 3400330Inactive· BRAWLEY, CA
Strong
Officer
9
ROGELIO SALAZAR
USDOT 3297035Inactive· EL CAMPO, TX
Strong
Officer
10
ROYS CONSTRUCTION LLC
USDOT 3867689Inactive· GAINESVILLE, GA
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

10 events
  1. 11/25/2019MCS-150 update filed

    0.0M mi reported (2018)

  2. 10/10/2019Insurance cancelled — VANTAPRO SPECIALTY INSURANCE COMPANY

    BIPD/Primary · policy 5087-0153-00

  3. 09/11/2019Insurance filed — VANTAPRO SPECIALTY INSURANCE COMPANY

    Liability (BIPD) — BMC-91X · policy 5087-0153-01

  4. 09/11/2019Insurance replaced — VANTAPRO SPECIALTY INSURANCE COMPANY

    BIPD/Primary · policy 5087-0153-00

  5. 10/24/2018Insurance cancelled — PROGRESSIVE COUNTY MUTUAL

    BIPD/Primary · policy CA 1740099

  6. 09/27/2018CONTRACT — INVOLUNTARY REVOCATION

    DISCONTINUED REVOCATION (10/01/2018)

  7. 09/11/2018Insurance replaced — PROGRESSIVE COUNTY MUTUAL

    BIPD/Primary · policy CA 1740099

  8. 05/21/2015MOTOR PROPERTY CONTRACT CARRIER — GRANTED
  9. 04/10/2015Insurance replaced — PROGRESSIVE COUNTY MUTUAL

    BIPD/Primary · policy CA 1740099

  10. 04/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

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2019-11-25
Reported mileage
1 mi (2018)
⚡

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