HaulerCheck · https://haulercheck.com/carrier/1987848-m-m-trans-llc/ · Checked 2026-10-19 08:42 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
M & M TRANS 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 average50.0% vs Nevada average 22.3%.
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, (702) 480-5805, not a number from an email or load board.
- Check that the MC number you were given is MC703421.
- 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) | MC703421 | Primary | NORTHLAND INSURANCE COMPANY Policy WN414868 · 91X | $750,000 | Nov 26, 2025 | 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 18, 2024 – Oct 18, 2026
4 of 8 · Nevada avg 22.3%
3 of 12 · Nevada avg 6.8%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Jul 1, 2026 | NV | 1 | 12 | Yes |
| Jun 12, 2026 | NV | 2 | 7 | Yes |
| May 28, 2026 | CA | 2 | 2 | Yes |
| Apr 13, 2026 | WY | 2 | 1 | Yes |
| Apr 11, 2026 | AL | 2 | 12 | Yes |
| Mar 26, 2026 | CO | 3 | 10 | Yes |
| Jan 16, 2026 | MT | 3 | 2 | Yes |
| Aug 6, 2025 | TX | 2 | 4 | No |
| Jul 25, 2025 | NM | 3 | 1 | No |
| May 15, 2025 | TX | 1 | 7 | 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 Nevada average covers 13,356 vehicle and 20,488 driver inspections of all Nevada-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
38 violations counted in FMCSA's Safety Measurement System (SMS), 10 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 59 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 | Nevada share |
|---|---|---|---|---|
| Vehicle Maintenance | 23 | 6 | 60.5% | 68.4% |
| Hours-of-Service Compliance | 12 | 4 | 31.6% | 18.2% |
| Unsafe Driving | 3 | 0 | 7.9% | 8.9% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| 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 | 4 | 4 |
| Lighting - Turn signal - Any inoperative on the rearmost vehicle. Lighting · Vehicle Maintenance · code 3939ALTSI | 2 | 1 |
| HOS (ELD) - On request by an authorized safety official a driver must produce and transfer from an ELD the driver's hours of service records in accordance with t Fail to transfer ELD records · Hours-of-Service Compliance · code 39524DELDPT | 2 | 0 |
| HOS (ELD) - Driver failing to review records and certify the accuracy of the information. Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1ELDDFR | 2 | 0 |
| Brake Out of Adjustment - Roto Clamp (Short & Long) DD-3 or Bolt Brakes Out of Adjustment · Vehicle Maintenance · code 39347E | 2 | 0 |
| Lighting - Clearance lamp(s) inoperative Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939ALCL | 2 | 0 |
| Wipers - Inoperative / missing / damaged wipers Windshield/ Glass/ Markings · Vehicle Maintenance · code 39378 | 2 | 0 |
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 1 | 1 |
| HOS (Property) - Driver produces a false record of duty status that concealed an HOS limitation violation after the last rest period. Explain: False Log · Hours-of-Service Compliance · code 3958EHOSPDOOS | 1 | 1 |
| HOS (Property) - Driving more than 11 hours following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Time Hours · Hours-of-Service Compliance · code 3953A1HOSPD | 1 | 1 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 18, 2026. "Share" is this company's mix of violations; the Nevada column is the mix across all Nevada-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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Jun 30, 2026 | Unknown, NV | 1 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 1987848 |
|---|---|
| MC / docket | MC703421 |
| Legal name | M & M TRANS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 2 |
| Drivers | 1 |
| Annual mileage | 190,853 (2025) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jan 26, 2010 · 16 years ago |
| Last MCS-150 update | May 5, 2026 |
Cargo carried
General FreightHousehold GoodsFresh ProduceMeatRefrigerated FoodBeveragesPaper Products
Questions about M & M TRANS LLC
What does M & M TRANS LLC's operating authority allow?
MC703421: Common carrier (may haul regulated property for hire for the general public).
Which information about M & M TRANS 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 M & M TRANS LLC?
Confirm the authority and insurance on the Motus record for USDOT 1987848. Call the company back on the phone number on file, (702) 480-5805, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC703421, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Las Vegas, NV →
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 08:42 UTC.