HaulerCheck · https://haulercheck.com/carrier/4315926-tridente-transports-llc/ · Checked 2026-10-19 22:17 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
TRIDENTE TRANSPORTS 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
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, (973) 393-1234, not a number from an email or load board.
- Check that the MC number you were given is MC1683082.
- 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) | MC1683082 | Primary | ACCREDITED SPECIALTY INSURANCE COMPANY Policy 2-CWS-UT-19-S0378141-00 · 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 19, 2024 – Oct 19, 2026
0 of 4 · Utah avg 23.6%
2 of 4 · Utah avg 4.5%
4 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Feb 11, 2026 | WV | 2 | 12 | No |
| Aug 4, 2025 | NY | 2 | 1 | No |
| Jan 22, 2025 | SC | 2 | 9 | Yes |
| Jan 14, 2025 | CO | 2 | 6 | 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 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
13 violations counted in FMCSA's Safety Measurement System (SMS), 2 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 28 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 | Utah share |
|---|---|---|---|---|
| Hours-of-Service Compliance | 8 | 2 | 61.5% | 12.6% |
| Vehicle Maintenance | 4 | 0 | 30.8% | 73.3% |
| Unsafe Driving | 1 | 0 | 7.7% | 9.8% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| HOS (Form) - Paper Log/Logging Programs Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 3958A | 2 | 0 |
| HOS (Property) - Failing to have a record of duty status using the method prescribed Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958A1HOSP | 1 | 1 |
| HOS (Property) - Failing to have in possession RODS for the previous seven consecutive days and available for inspection while on duty Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958K2HOSP | 1 | 1 |
| 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 | 0 |
| 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 | 0 |
| Driving beyond 8 hour driving limit since the end of the last on duty off duty or sleeper berth period of at least 30 consecutive minutes Hours · Hours-of-Service Compliance · code 3953AII | 1 | 0 |
| HOS (ELD) - Driver failed to review any unassigned driving time when prompted by the ELD Incomplete/Wrong Log · Hours-of-Service Compliance · code 39532BELDDFR | 1 | 0 |
| State/Local Laws - Speeding basic rule/speed too fast for conditions Dangerous Driving · Unsafe Driving · code 3922SLTFC | 1 | 0 |
| Other - Any air leak not attributed to the brake or suspension system. Brakes All Others · Vehicle Maintenance · code 3963A1OAL | 1 | 0 |
| Lighting - Identification lamp(s) inoperative Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939ALIL | 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 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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Jan 22, 2025 | Dillon, SC | 0 | 3 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 4315926 |
|---|---|
| MC / docket | MC1683082 |
| Legal name | TRIDENTE TRANSPORTS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 1 |
| Drivers | 1 |
| Annual mileage | 1,500 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Oct 29, 2024 · 1 year ago |
| Last MCS-150 update | Nov 24, 2025 |
Cargo carried
General Freight
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 TRIDENTE TRANSPORTS LLC
What does TRIDENTE TRANSPORTS LLC's operating authority allow?
MC1683082: Common carrier (may haul regulated property for hire for the general public).
Which information about TRIDENTE TRANSPORTS 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. There are too few vehicle inspections in the last 24 months to judge the out-of-service rate. 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 TRIDENTE TRANSPORTS LLC?
Confirm the authority and insurance on the Motus record for USDOT 4315926. Call the company back on the phone number on file, (973) 393-1234, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1683082, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Vernal, UT →
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:17 UTC.