CSA
Authorized · PropertyUSDOT 1182959· MX472673· CARRIER· EIN 98-0432503
⬇ PDF report

RIVERA TRANSPORT

Legal: SEBASTIAN RIVERA DURAN

16 DE SEPTIEMBRE, TIJUANA, BN, 22390(664) 901-2653SEBASTIAN RIVERA DURAN
Vetting snapshot
Authority
Active
operating authority
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.

Authority & insurance

MX472673

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

Common
Active
Contract
None
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
not required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (1) ▾
11/05/2003FOR HIRE PROPERTYGRANTED

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
2
on file (MCS-150)
Drivers
2
2 hold a CDL
Annual mileage
0M mi
reported 2013
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi2 drivers
Company officer
SEBASTIAN RIVERA DURAN
Operation
Interstate
Registered since
2003-10-29
Last MCS-150 update
2014-06-26
Census status
I

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

Connections

carrier graph

This carrier shares addresses with 3 other carriers — review the connections below as part of your vetting.

3
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
0
Strong links
Medium· 3
IRVING JULIAN NAVARRO PINAL
USDOT 2318859Inactive· SAN DIEGO, CA
Medium
Mailing
LUIS ALBERTO RAMIREZ CASTRO
USDOT 2641579Inactive· SAN DIEGO, CA
Medium
Mailing
SERGIO IRAK MARTINEZ BELTRAN
USDOT 4085089Inactive· SAN DIEGO, CA
Medium
Mailing

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. 06/26/2014MCS-150 update filed

    0.0M mi reported (2013)

  2. 11/05/2003FOR HIRE PROPERTY — GRANTED
  3. 10/29/2003Registered 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
2014-06-26
Reported mileage
4,230 mi (2013)
⚡

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