CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides8
Driver CoachingAPI
LoginRegisterTry FleetTrained
Not AuthorizedUSDOT 2427722· MC836632· CARRIER· EIN 46-2806955
⬇ PDF report

ROAD LIMATT

2827 CRESTBROOK BEND LN, KATY, TX, 77449(713) 582-2346roadlimattinc@gmail.comCARLOS ROMERO
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
$750K required — verify
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
0
/ 100

Risk factors

High riskVioCodes score
Operating authority is not activeNo active liability (BIPD) insurance filing on file

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

MC836632

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

No active liability (BIPD) insurance filing on file
Common
None
Contract
Inactive
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
$750K required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (1) ▾
08/28/2013MOTOR PROPERTY CONTRACT CARRIERGRANTED→ REVOKED (03/31/2014)
Insurance history2 insurers on record
Filing timeline (2) ▾
  1. HALLMARK COUNTY MUTUAL INSURANCE COMPANY$750KCancelled
    BIPD/Primary · eff 10/14/2013 → 03/23/2014
  2. PROGRESSIVE COUNTY MUTUAL$750KReplaced
    BIPD/Primary · eff 08/11/2013 → 10/14/2013

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
3
on file (MCS-150)
Drivers
3
3 hold a CDL
Annual mileage
0M mi
reported 2012
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi3 drivers
Company officer
CARLOS ROMERO
Operation
Interstate
Registered since
2013-08-07
Last MCS-150 update
2013-08-07
Census status
I

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

Activity history

5 events
  1. 03/23/2014Insurance cancelled — HALLMARK COUNTY MUTUAL INSURANCE COMPANY

    BIPD/Primary · policy TXA518104

  2. 10/14/2013Insurance replaced — PROGRESSIVE COUNTY MUTUAL

    BIPD/Primary · policy CA 2299127

  3. 08/28/2013MOTOR PROPERTY CONTRACT CARRIER — GRANTED

    REVOKED (03/31/2014)

  4. 08/07/2013Registered with FMCSA

    AUTHORIZED FOR HIRE

  5. 08/07/2013MCS-150 update filed

    0.0M mi reported (2012)

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
2013-08-07
Reported mileage
10,000 mi (2012)
⚡

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