HaulerCheck · https://haulercheck.com/carrier/2164403-confort-travel-llc/ · Checked 2026-10-19 22:47 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
CONFORT TRAVEL LLC
No risk signals in the last-known data
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. Authority and insurance are last known from May 14, 2026.
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.
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, (520) 980-0798, not a number from an email or load board.
- Check that the MC number you were given is MC752053.
- 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) | MC752053 | Primary | PRIME INSURANCE COMPANY Policy SC25090626 · 91X | $5,000,000 | Sep 17, 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 19, 2024 – Oct 19, 2026
1 of 38 · Arizona avg 22.3%
11 of 84 · Arizona avg 4.5%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 26, 2026 | CA | 1 | 3 | Yes |
| Aug 14, 2026 | NV | 1 | 2 | No |
| Aug 14, 2026 | NV | 1 | 2 | No |
| Jul 29, 2026 | CA | 3 | 2 | No |
| Jul 17, 2026 | US | 3 | 0 | No |
| Jul 17, 2026 | US | 3 | 0 | No |
| Jul 4, 2026 | LA | 2 | 3 | Yes |
| Jun 30, 2026 | US | 1 | 1 | No |
| Jun 27, 2026 | LA | 2 | 1 | No |
| Jun 26, 2026 | LA | 2 | 7 | 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 Arizona average covers 53,982 vehicle and 81,935 driver inspections of all Arizona-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
61 violations counted in FMCSA's Safety Measurement System (SMS), 12 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 76 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 | Arizona share |
|---|---|---|---|---|
| Vehicle Maintenance | 31 | 2 | 50.8% | 75.7% |
| Hours-of-Service Compliance | 13 | 0 | 21.3% | 12.1% |
| Driver Fitness | 11 | 9 | 18.0% | 3.5% |
| Unsafe Driving | 5 | 0 | 8.2% | 8.1% |
| Controlled Substances/Alcohol | 1 | 1 | 1.6% | 0.1% |
10 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 | 6 | 6 |
| Windshield - Damaged or Discolored Windshield/ Glass/ Markings · Vehicle Maintenance · code 39360C | 5 | 0 |
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 3 | 0 |
| HOS (Form) - Paper Log/Logging Programs Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 3958A | 3 | 0 |
| Air Brake - Audible air leak at a proper connection Brakes All Others · Vehicle Maintenance · code 39345DB | 3 | 0 |
| Medical (Certificate) - Operating a commercial vehicle without corrective lenses or hearing aid as indicated on the driver's medical certificate Physical · Driver Fitness · code 39141B10MC | 2 | 2 |
| Border Zone - Driver cannot satisfy the English language proficiency requirements of 391.11(b)(2) in accordance with the current corresponding FMCSA enforcement General Driver Qualification · Driver Fitness · code 39111B2Z | 2 | 0 |
| HOS (ELD) - In-Vehicle Information - Failing to have an instruction sheet for the driver describing ELD malfunction reporting requirements and recordkeeping proce EOBR Related · Hours-of-Service Compliance · code 39522H3ELDMF | 2 | 0 |
| HOS (ELD) - Driver failing to certify the record immediately after the final required entry has been made or corrected for the 24 hour period. Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B2ELDDFC24 | 2 | 0 |
| State/Local Laws - Speeding 11-14 miles per hour over the speed limit Speeding 3 · Unsafe Driving · code 3922SLLS3 | 2 | 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 Arizona column is the mix across all Arizona-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 | 2164403 |
|---|---|
| MC / docket | MC752053 |
| Legal name | CONFORT TRAVEL LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 20 |
| Drivers | 42 |
| Annual mileage | 460,347 (2025) |
| Hazmat | No |
| Safety rating | Satisfactory (Jan 23, 2026) |
| USDOT number added | Jun 16, 2011 · 15 years ago |
| Last MCS-150 update | Feb 27, 2026 |
Cargo carried
Passengers
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 CONFORT TRAVEL LLC
What does CONFORT TRAVEL LLC's operating authority allow?
MC752053: Common carrier (may haul regulated property for hire for the general public).
Which information about CONFORT TRAVEL 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.
What should I verify before booking CONFORT TRAVEL LLC?
Confirm the authority and insurance on the Motus record for USDOT 2164403. Call the company back on the phone number on file, (520) 980-0798, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC752053, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Nogales, AZ →
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-19 22:47 UTC.