CSA
UnknownUSDOT 2781818· CARRIER
⬇ PDF report

FEDERICO RODRIGUEZ

SUPER PALI 5 CDRAS AL ESTE SEBACO MATAGALPA, NICARAGUA, NI, 6220050588935581infoext2014@gmail.comFEDERICO RODRIGUEZ
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%

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
1
0 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi1 drivers
Company officer
FEDERICO RODRIGUEZ
Operation
Interstate · Hazmat
Registered since
2015-07-15
Last MCS-150 update
2015-07-13
Census status
I

Fleet: 1 trucks · 1 owned tractors · 1 owned trailers.

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, officers or emails with 16 other carriers — review the connections below as part of your vetting.

16
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
13
Strong links
Strong· 13
1
ANDRES RAMIREZ VEGA
USDOT 2785864Inactive· PALM BEACH, FL
Strong
Email
2
CARLOS HUMBERTO CATALAN
USDOT 3206398Inactive· CHANNELVIEW, TX
Strong
Email
3
DAVID & FEDERICO RODRIGUEZ
USDOT 2869800Inactive· VAN NUYS, CA
Strong
Officer
4
DENIS N OROZCO
USDOT 2925740Inactive· HOUSTON, TX
Strong
Email
5
ERLIN RAUL PAZ
USDOT 3152111Active· HOUSTON, TX
Strong
Email
6
ERLING OROZCO CASTELLON
USDOT 2779392Inactive· NICARAGUA, NI
Strong
Email
7
FEDERICO & NICHOLE RODRIGUEZ
USDOT 2273975Active· DEARBORN HEIGHTS, MI
Strong
Officer
8
FEDERICO RODRIGUEZ
USDOT 2810551Active· POMONA, CA
Strong
Officer
9
FEDERICO RODRIGUEZ
USDOT 2581986Inactive· MIAMI, FL
Strong
Officer
10
JULIO GERARDO ESTRADA FONSECA
USDOT 2515116Inactive· HOUSTON, TX
Strong
Email
11
MVD GROUP CORP
USDOT 2914243Inactive· FONTANA, CA
Strong
Officer
12
SAMUEL OSORIO GOMEZ
USDOT 1922013Inactive· PUERTO SAN JOSE ESCUENTLA, GT
Strong
Email
13
TRANSPORTES GENERALES SA
USDOT 2934248Inactive· HOUSTON, TX
Strong
Email
Medium· 3
FRANK SOLERA
USDOT 2802583Inactive· ALAJUELA, CR
Medium
Mailing
HENRY LEWIS
USDOT 2796327Inactive· GUATEMALA, GT
Medium
Mailing
HUGO PALOMO
USDOT 2816299Inactive· GUATEMALA, GT
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

2 events
  1. 07/15/2015Registered with FMCSA

    PRIVATE PROPERTY

  2. 07/13/2015MCS-150 update filed

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2015-07-13
Reported mileage
—
⚡

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