HaulerCheck · https://haulercheck.com/carrier/2419167-runningman-transport-llc/ · Checked 2026-10-20 08:12 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
RUNNINGMAN TRANSPORT LLC
Review before booking · 1 signal
How risk signals workFacts from the FMCSA record that call for a closer look. They are not a finding of wrongdoing. Authority and insurance are last known from May 14, 2026.
- Vehicle out-of-service rate well above the state average44.4% vs Texas average 25.1%.
No cargo cover filed with FMCSA
Not a live check. FMCSA has not published a Motus record for this carrier, so authority and insurance show the last known status from May 14, 2026. Confirm on Motus ↗ before booking.
What to verify next
- Confirm authority and insurance on the official Motus record ↗: our copy is the last known status from May 14, 2026. Safety record: SAFER ↗.
- Call back on the number on file, (214) 729-3368, not a number from an email or load board.
- Check that the MC number you were given is MC833104.
- 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) | MC833104 | Primary | PROGRESSIVE COUNTY MUTUAL Policy CA874037927 · 91X | $750,000 | May 13, 2026 | Active |
Source: Last known · FMCSA snapshot May 14, 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.
Last known filings. Insurance for this carrier comes from the FMCSA snapshot of May 14, 2026. Policies may have been cancelled or replaced since. Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.
Roadside inspections Oct 19, 2024 – Oct 19, 2026
4 of 9 · Texas avg 25.1%
0 of 11 · Texas avg 7.7%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Aug 12, 2026 | NM | 1 | 10 | Yes |
| Feb 11, 2026 | LA | 3 | 1 | No |
| Dec 29, 2025 | NM | 3 | 1 | No |
| Nov 17, 2025 | TX | 2 | 5 | Yes |
| Oct 12, 2025 | NM | 2 | 1 | Yes |
| Sep 21, 2025 | NM | 2 | 0 | No |
| Aug 12, 2025 | TX | 2 | 8 | No |
| Jun 10, 2025 | TX | 2 | 0 | No |
| Mar 14, 2025 | TX | 2 | 6 | No |
| Dec 16, 2024 | CA | 1 | 3 | Yes |
How these rates are calculated
Period: Oct 19, 2024 – Oct 19, 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,522 vehicle and 460,240 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
26 violations counted in FMCSA's Safety Measurement System (SMS), 6 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 36 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 19, 2024 – Oct 19, 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 |
|---|---|---|---|---|
| Vehicle Maintenance | 24 | 6 | 92.3% | 78.8% |
| Hours-of-Service Compliance | 2 | 0 | 7.7% | 11.4% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Tire-flat and/or audible air leak Tires · Vehicle Maintenance · code 39375A3 | 2 | 2 |
| Driver failed to certify the accuracy of the information gathered by the ELD Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1 | 2 | 0 |
| Brake Out of Adjustment - Roto Clamp (Short & Long) DD-3 or Bolt Brakes Out of Adjustment · Vehicle Maintenance · code 39347E | 2 | 0 |
| Inoperable Required Lamp Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939 | 2 | 0 |
| Brake - Defective brake(s) are equal to or greater than 20% of the service brakes on the vehicle/combination Brake Out Of Service · Vehicle Maintenance · code 3963A1BOS | 1 | 1 |
| Air Brake - Inoperable or missing tractor protection valve Brakes All Others · Vehicle Maintenance · code 39343ATPV | 1 | 1 |
| Air Brake - Fails air loss rate test Brakes All Others · Vehicle Maintenance · code 3963A1BALR | 1 | 1 |
| Tires - All others leaking or inflation less than 50% of the maximum inflation pressure on tire not equipped with ATIS Tires · Vehicle Maintenance · code 39375A3TAOL | 1 | 1 |
| CMV manufactured after 10/19/94 has an automatic airbrake adjustment system that fails to compensate for wear Brakes All Others · Vehicle Maintenance · code 39353B | 1 | 0 |
| Air Brake - CMV manufactured on or after 10/20/1994 has an automatic airbrake adjustment system that fails to compensate for wear Brakes All Others · Vehicle Maintenance · code 39353BB | 1 | 0 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 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 19, 2024 – Oct 19, 2026
No reportable crashes in this period.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 2419167 |
|---|---|
| MC / docket | MC833104 |
| Legal name | RUNNINGMAN TRANSPORT LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 3 |
| Drivers | 4 |
| Annual mileage | 221,584 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jul 3, 2013 · 13 years ago |
| Last MCS-150 update | May 4, 2026 |
Cargo carried
General FreightHousehold GoodsBuilding MaterialsFresh ProduceIntermodal ContainersMeatRefrigerated FoodBeveragesPaper ProductsConstructionOtherSeafood
Change history
No changes to name, contact details, authority or insurance since we started tracking on Oct 18, 2026. We compare every company's FMCSA record each day.
to see it on your watchlist when something changes.
Questions about RUNNINGMAN TRANSPORT LLC
What does RUNNINGMAN TRANSPORT LLC's operating authority allow?
MC833104: Common carrier (may haul regulated property for hire for the general public); Contract carrier (may haul regulated property for hire under continuing contracts with specific shippers).
Which information about RUNNINGMAN TRANSPORT LLC is old or missing?
Operating authority is the last known status from the FMCSA snapshot of May 14, 2026, not a current check. Insurance filings are from the same May 14, 2026 snapshot. 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 RUNNINGMAN TRANSPORT LLC?
Confirm the authority and insurance on the Motus record for USDOT 2419167. Call the company back on the phone number on file, (214) 729-3368, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC833104, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Dallas, TX →
Company details from the FMCSA Company Census File (Oct 19, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).
Page generated 2026-10-20 08:12 UTC.