ARMENTEROS TRANSPORTATION LLC

Salt Lake City, UT · Interstate · 8 power units · Not rated · USDOT since Aug 8, 2019 (7 years)

Review before booking · 1 signal

How risk signals work

Facts 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 average40.0% vs Utah average 23.6%.
Confirm on Motus ↗ Call (801) 548-3663 Safety: SAFER ↗
Operating authority
Active on 1 of 2 dockets
FF48742: no authority granted
MC1056390: Common carrier active
Last known · FMCSA snapshot May 14, 2026
Liability insurance (BI&PD)
$1,000,000
Required minimum: $1,000,000
No cargo cover filed with FMCSA
Last known · FMCSA snapshot May 14, 2026
Vehicle out-of-service rate
40.0%
2 of 5 vehicle inspections (small sample) · Utah avg 23.6%
FMCSA inspections · Oct 19, 2024 – Oct 19, 2026

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.

Confirm on Motus ↗Call

Operating authority

FF48742 Last known · FMCSA snapshot May 14, 2026

Operating authorityNot authorized
FMCSA has not granted common, contract, broker or forwarder authority on this docket.

MC1056390 Last known · FMCSA snapshot May 14, 2026

Common carrier
Common Carrier
Active
Liability insurance on file$1,000,000 (required: $1,000,000)

Last known status. This authority record comes from the FMCSA snapshot of May 14, 2026, the last one published before FMCSA moved registration to Motus. It may have changed since. Confirm current authority: Motus record for USDOT 3320361 ↗

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.

TypeDocketLayerInsurerCoverageEffectiveStatus
Liability (BI&PD)MC1056390PrimaryBENCHMARK INSURANCE COMPANY
Policy FLCA-1926-05238 · 91X
$1,000,000Oct 11, 2025Active

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

18inspections
40.0%vehicle out-of-service
2 of 5 · Utah avg 23.6%
22.2%driver out-of-service
4 of 18 · Utah avg 4.5%
30violations written on inspection reports
10 most recent inspections
DateStateLevelViolationsOut of service
Aug 21, 2026NV21Yes
Jul 14, 2026NV31Yes
Jul 9, 2026UT16No
Jun 30, 2026UT34No
May 12, 2026UT30No
Apr 4, 2026UT30No
Apr 4, 2026UT32Yes
Feb 3, 2026AZ34No
Jan 6, 2026UT30No
Nov 13, 2025CA22Yes
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 Utah average covers 22,772 vehicle and 39,441 driver inspections of all Utah-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

21 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 30 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)ViolationsOut of serviceShareUtah share
Vehicle Maintenance9242.9%73.3%
Hours-of-Service Compliance6228.6%12.6%
Unsafe Driving4019.0%9.8%
Driver Fitness229.5%3.3%
10 most frequent violations
ViolationTimesOut of service
HOS (Property) - No driver may make a false report in connection with a duty status. Explain
False Log · Hours-of-Service Compliance · code 3958EHOSPD
21
Operating a CMV without documentation of a periodic inspection
Inspection Reports · Vehicle Maintenance · code 39617CPI
20
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
11
License (CDL) - Operate a CMV and does not possess a valid CDL
License-related: High · Driver Fitness · code 38323A2LCDLN
11
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
11
Lighting - Turn signal - Any inoperative on the rearmost vehicle.
Lighting · Vehicle Maintenance · code 3939ALTSI
11
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
11
HOS - False record of duty status driver improper use of Personal Conveyance - Not OOS
False Log · Hours-of-Service Compliance · code 3958E1PC
10
HOS (ELD) - ELD Form and Manner
Other Log/Form & Manner · Hours-of-Service Compliance · code 39524
10
HOS (ELD) - Driver failing to review records and certify the accuracy of the information.
Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1ELDDFR
10

Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 2026. "Share" is this company's mix of violations; the Utah column is the mix across all Utah-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 number3320361
MC / docketFF48742, MC1056390
Legal nameARMENTEROS TRANSPORTATION LLC
OperationInterstate
Business type—
Power units8
Drivers9
Annual mileage900,410 (2025)
HazmatNo
Safety ratingNot rated (no compliance review on record)
USDOT number addedAug 8, 2019 · 7 years ago
Last MCS-150 updateMay 6, 2026

Cargo carried

General FreightMotor VehiclesFresh ProduceMeatRefrigerated Food

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 ARMENTEROS TRANSPORTATION LLC

What does ARMENTEROS TRANSPORTATION LLC's operating authority allow?

MC1056390: Common carrier (may haul regulated property for hire for the general public).

Which information about ARMENTEROS TRANSPORTATION 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 ARMENTEROS TRANSPORTATION LLC?

Confirm the authority and insurance on the Motus record for USDOT 3320361. Call the company back on the phone number on file, (801) 548-3663, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches FF48742 or MC1056390, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.

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 23:36 UTC.