HaulerCheck · https://haulercheck.com/carrier/3818971-bahati-express-llc/ · Checked 2026-10-19 10:05 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: FMCSA Motus · Oct 18, 2026
BAHATI EXPRESS LLC
No risk signals found
How risk signals workNothing in the FMCSA record matched our risk signals. That is not a guarantee, and it does not confirm who you are talking to; follow the checks below.
No cargo cover filed with FMCSA
Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.
What to verify next
- Confirm authority and insurance on the official Motus record ↗. Safety record: SAFER ↗.
- Call back on the number on file, (832) 727-3527, not a number from an email or load board.
- Check that the MC number you were given is MC1381224.
- Ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Insurance on file
Liability (BI&PD) pays for injury and damage to other people and property; it does not cover the freight. Cargo insurance covers the freight. FMCSA only requires cargo filings from household goods carriers and freight forwarders, so most carriers file none: ask for a cargo certificate that fits your load. No cargo cover filed with FMCSA.
| Type | Docket | Layer | Insurer | Coverage | Effective | Status |
|---|---|---|---|---|---|---|
| Liability (BI&PD) | MC1381224 | Primary | Trisura Specialty Insurance Company Policy FOP133652026 · BMC-91X | $750,000 | Feb 28, 2026 | Active |
Source: FMCSA Motus · Oct 18, 2026. Identical filings repeated in the FMCSA data are shown once; a filing listed under two dockets is one policy, not extra coverage. Coverage is the maximum amount filed with FMCSA, not the full policy.
Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.
Roadside inspections Oct 18, 2024 – Oct 18, 2026
0 of 8 · Texas avg 25.1%
1 of 15 · Texas avg 7.7%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 6, 2026 | TN | 3 | 0 | No |
| Sep 9, 2026 | TX | 2 | 0 | No |
| Sep 3, 2026 | KY | 2 | 0 | No |
| Aug 28, 2026 | WA | 1 | 2 | No |
| Aug 11, 2026 | IA | 3 | 1 | No |
| Jul 9, 2026 | OR | 2 | 0 | No |
| Jun 30, 2026 | NV | 3 | 1 | Yes |
| Jun 25, 2026 | NC | 3 | 0 | No |
| Jun 11, 2026 | NC | 3 | 0 | No |
| May 11, 2026 | TX | 2 | 0 | No |
How these rates are calculated
Period: Oct 18, 2024 – Oct 18, 2026. Vehicle rate = vehicle inspections with a vehicle out-of-service order ÷ vehicle inspections (levels 1, 2, 5 and 6). Driver rate uses levels 1, 2, 3 and 6. The Texas average covers 347,521 vehicle and 460,200 driver inspections of all Texas-based carriers in this period. It mixes every type of operation, so compare with care; rates based on a handful of inspections say little. FMCSA's own SMS measures are weighted differently: SMS profile ↗ · SAFER snapshot ↗
Violations in FMCSA's SMS last 24 months
2 violations counted in FMCSA's Safety Measurement System (SMS), 1 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 4 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 18, 2024 – Oct 18, 2026 window. The SMS count comes from FMCSA's own monthly SMS snapshot, which uses its own 24-month window and only the violations it scores. Both are FMCSA figures; they measure different things.
| Category (FMCSA BASIC) | Violations | Out of service | Share | Texas share |
|---|---|---|---|---|
| Driver Fitness | 1 | 1 | 50.0% | 4.2% |
| Hours-of-Service Compliance | 1 | 0 | 50.0% | 11.4% |
2 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Driver cannot satisfy the English language proficiency requirements of 391.11(b)(2) in accordance with the current corresponding FMCSA enforcement guidance (391. General Driver Qualification · Driver Fitness · code 39111B2Q | 1 | 1 |
| HOS (ELD) - Driver failing to review records and certify the accuracy of the information. Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1ELDDFR | 1 | 0 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 18, 2026. "Share" is this company's mix of violations; the Texas column is the mix across all Texas-based carriers, so you can see which kinds of problems stand out. A high count partly reflects fleet size and how often trucks are inspected.
Crashes Oct 18, 2024 – Oct 18, 2026
No reportable crashes in this period.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 3818971 |
|---|---|
| MC / docket | MC1381224 |
| Legal name | BAHATI EXPRESS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 10 |
| Drivers | 26 |
| Annual mileage | 145,658 (2025) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Feb 10, 2022 · 4 years ago |
| Last MCS-150 update | Jun 20, 2026 |
Cargo carried
General FreightBuilding MaterialsMachinery, Large ObjectsPaper ProductsAgricultural/Farm SuppliesConstructionOtherOther
Questions about BAHATI EXPRESS LLC
What does BAHATI EXPRESS LLC's operating authority allow?
MC1381224: Motor carrier (may haul regulated property for hire).
Which information about BAHATI EXPRESS LLC is old or missing?
FMCSA has not issued a safety rating, which means no compliance review is on record, not that the carrier is unsafe.
What should I verify before booking BAHATI EXPRESS LLC?
Confirm the authority and insurance on the Motus record for USDOT 3818971. Call the company back on the phone number on file, (832) 727-3527, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1381224, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Houston, TX →
Company details from the FMCSA Company Census File (Oct 18, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).
Page generated 2026-10-19 10:05 UTC.