CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 1920094· CARRIER· EIN 80-0256506
⬇ PDF report

ARMANDO RIVERA

739 LARGO LN, MACCLENNY, FL, 32063(904) 657-1828ARMANDO RIVERA
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
—
Annual mileage
0.1M mi
reported 2010
Recordable crash rate
—
per million miles
Company officer
ARMANDO RIVERA
Operation
Intrastate (Non-Hazmat)
Registered since
2009-07-29
Last MCS-150 update
2012-07-30
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.

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

11
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
11
Strong links
Strong· 11
1
3R TRUCKING & PIPE LLC
USDOT 2414067Inactive· COLORADO CITY, TX
Strong
Officer
2
A & R EXPRESS TRUCKING INC
USDOT 3884362Inactive· WEST COVINA, CA
Strong
Officer
3
ARLEC TRANSPORT INDUSTRIES INC
USDOT 2066909Inactive· NORTH RIVERSIDE, IL
Strong
Officer
4
ARMANDO RIVERA
USDOT 2144684Inactive· NORTH RIVERSIDE, IL
Strong
Officer
5
ARMANDO RIVERA
USDOT 2469153Active· HOUSTON, TX
Strong
Officer
6
ARMANDO RIVERA
USDOT 2763964Inactive· RIALTO, CA
Strong
Officer
7
ENVOY XPRESS INC
USDOT 3962021Inactive· PHOENIX, AZ
Strong
Officer
8
ESCALANTE TRANSPORT INC
USDOT 3801327Active· NORTHLAKE, IL
Strong
Officer
9
HAZEL TRUCKING LLC
USDOT 2316058Active· KEARNS, UT
Strong
Officer
10
RIVER H LOGISTICS LLC
USDOT 3829726Inactive· MAUMELLE, AR
Strong
Officer
11
TROYA TRUCKING LLC
USDOT 3335223Inactive· LONGBEACH, CA
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. 07/30/2012MCS-150 update filed

    0.1M mi reported (2010)

  2. 07/29/2009Registered 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
2012-07-30
Reported mileage
100,000 mi (2010)
⚡

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