Loading…
DOT 2190482 is operated by OSMAN ALEXI GONZALES BARAHONA out of Lanham, MD. This profile shows verified operating authority, current insurance, observed equipment, and recent inspection activity joined into one card so brokers can verify the carrier in one tab.
Operating authority is verified against the live public registry and refreshed daily. Current status: unknown. "active" means the carrier is authorized to operate; "inactive" or "out-of-service" indicates the carrier should not be hauling.
Liability and cargo insurance status is drawn from the latest filings on record. Current status: unknown. We mark a carrier "lapsed" when the most recent cancellation date is in the past with no superseding policy.
OSMAN ALEXI GONZALES BARAHONA was last inspected on 2026-10-07. We've recorded 1 inspections in the trailing 12 months.
OSMAN ALEXI GONZALES BARAHONA does not have an MC number on file. Some carriers operate intrastate-only or under a private-carrier exemption and never apply for one.
See the 1 fraud signal on OSMAN ALEXI GONZALES BARAHONA— free signup
Step-by-step checklist for vetting any motor carrier before tendering a load — operating authority, insurance, safety scores, inspection history, and identity flags.
How double brokering works in 2026, recent fraud patterns, and a prevention checklist for freight brokers and shippers who want to stop the bleed.
Evidence, severity, and resolution notes for each signal on this carrier.
Consider with verification — at least one signal needs review.
power units (MCS-150)
distinct VINs in inspections
1 inspections, 12mo
most recent roadside record
Not enough broker-reported loads yet — this score unlocks as brokers report load outcomes. Aggregates appear once 3+ brokerages have reported on this carrier (0 loads from 0 brokerages so far).
Not enough reports yet
0 of 3 brokers needed before rates unlock
Rates stay locked below 3 contributing brokers so no single broker’s loads can be picked out of the aggregate.
No community reports for this carrier. Had a fraud or cargo-theft incident? Your report warns the whole network within minutes.
Community reports are submitted by broker workspaces and are NOT verified by KnowHaul. New reporters are human-moderated; 3+ corroborating workspaces feed a capped penalty into the fraud risk score. Named in a report that's wrong? Email admin@knowhaul.com and a human will review it.
Not enough claim reports yet
0 of 3 brokers needed before claims history unlocks
Claims stay locked below 3 contributing brokers so no single broker's claims can be picked out of the aggregate.
Aggregate rating unlocks at 3 reviewing workspaces — 0 so far. Individual reviews appear below as they're published.
No published reviews yet. Worked with this carrier? Your review starts the record.
Current reported fleet · as of Sep 2011. A trend line appears once a second filing is on record.
These are our estimates from local roadside-inspection history; FMCSA hasn't published measures for this carrier yet (see #1000).
Crash Indicator and Hazmat Compliance percentiles aren't published in the public SMS downloads today (see #832).
Signals are precursor patterns, not proof of fraud. Verify before acting — and if a flag looks wrong, dispute it from its row.
Matched on equipment mix, fleet-size band, and home state.
Authority reactivated on 2026-10-07 after going dormant on 2025-07-21 — the classic chameleon-MC pattern.
No equipment signal — request a COI before tender.