CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 2173373· CARRIER· EIN 45274859
⬇ PDF report

MRX TRUCKING

3727 85TH STREET APT 24, JACKSON HEIGHTS, NY, 11372(347) 951-7184mikeram79@hotmail.comMICHAEL RAMIREZ
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
1
0 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi1 drivers
Company officer
MICHAEL RAMIREZ
Operation
Intrastate (Non-Hazmat)
Registered since
2011-07-15
Last MCS-150 update
2014-06-30
Census status
Active

Fleet: 1 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 officers with 12 other carriers — review the connections below as part of your vetting.

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
12
Strong links
Strong· 12
1
ALL AMERICAN MASONRY INC
USDOT 3240159Active· FORT COLLINS, CO
Strong
Officer
2
BNM HAULING LLC
USDOT 3233566Inactive· ENNIS, TX
Strong
Officer
3
BNM HAULING LLC
USDOT 2898210Inactive· ENNIS, TX
Strong
Officer
4
COLORADO TILE CONTRACTORS
USDOT 1837235Active· CASTLE ROCK, CO
Strong
Officer
5
EMRG CORP
USDOT 2531101Inactive· MIDLAND, TX
Strong
Officer
6
MICHAEL RAMIREZ
USDOT 2567079Active· ODESSA, TX
Strong
Officer
7
MICHAEL RAMIREZ & LUIS VARGAS COLMENARES
USDOT 1219221Active· ENSENADA, BN
Strong
Officer
8
MNG TRANSPORT LLC
USDOT 5659472Active· PALMDALE, CA
Strong
Officer
9
MRX DRYWALL LLC
USDOT 4098424Active· CHELSEA, MA
Strong
Officer
10
NATIONAL STEEL FABRICATION LLC
USDOT 4475624Active· WARMINSTER, PA
Strong
Officer
11
PROVIDENT LOGISTICS LLC
USDOT 3797408Active· BROOKLYN, NY
Strong
Officer
12
SVR TRUCKING LLC
USDOT 3917685Inactive· SAN ANTONIO, TX
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. 06/30/2014MCS-150 update filed
  2. 07/15/2011Registered 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
2014-06-30
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 23, 2026, 2:50 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.