ROYAL ROUTE INC

Marysville, WA · Interstate · 2 power units · Not rated · USDOT since Jan 26, 2026 (8 months)

No risk signals found

How risk signals work

Nothing 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.

Confirm on Motus ↗ Call (425) 309-2008 Safety: SAFER ↗
Operating authority
Active
MC1792888: Motor carrier active
FMCSA Motus · Oct 19, 2026
Liability insurance (BI&PD)
$750,000
Required minimum: $750,000
No cargo cover filed with FMCSA
FMCSA Motus · Oct 19, 2026
Vehicle out-of-service rate
0.0%
Only 1 vehicle inspection; too few to compare
FMCSA inspections · Oct 19, 2024 – Oct 19, 2026

Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.

Confirm on Motus ↗Call

Operating authority

MC1792888 FMCSA Motus · Oct 19, 2026

Motor carrier
Motor Carrier of Property (Except Household Goods)
Active
Liability insurance on file$750,000 (required: $750,000)

Confirm current authority: Motus record for USDOT 4524047 ↗

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)MC1792888—EVOLUM RISK RETENTION GROUP, INC.
Policy POCL00000807 · BMC-91X
$750,000May 19, 2026Active

Source: FMCSA Motus · Oct 19, 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.

Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.

Roadside inspections Oct 19, 2024 – Oct 19, 2026

2inspections
0.0%vehicle out-of-service
0 of 1 · Washington avg 24.5%
50.0%driver out-of-service
1 of 2 · Washington avg 4.9%
11violations written on inspection reports
2 most recent inspections
DateStateLevelViolationsOut of service
Apr 21, 2026CA20No
Apr 10, 2026CO311Yes
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 Washington average covers 48,855 vehicle and 83,396 driver inspections of all Washington-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

4 violations counted in FMCSA's Safety Measurement System (SMS), 1 of them serious enough to put the driver or vehicle out of service.

Why is this different from the 11 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 serviceShareWashington share
Hours-of-Service Compliance3075.0%12.4%
Driver Fitness1125.0%3.9%
4 most frequent violations
ViolationTimesOut of service
License (CDL) - Operate a CMV and does not possess a valid CDL
License-related: High · Driver Fitness · code 38323A2LCDLN
11
HOS (Property) - No driver may make a false report in connection with a duty status. Explain
False Log · Hours-of-Service Compliance · code 3958EHOSPD
10
HOS (ELD) - Driver failed to review any unassigned driving time when prompted by the ELD
Incomplete/Wrong Log · Hours-of-Service Compliance · code 39532BELDDFR
10
HOS (Form) - Paper Log/Logging Programs Form and Manner
Other Log/Form & Manner · Hours-of-Service Compliance · code 3958A
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 Washington column is the mix across all Washington-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 number4524047
MC / docketMC1792888
Legal nameROYAL ROUTE INC
OperationInterstate
Business type—
Power units2
Drivers2
Annual mileage15,090 (2025)
HazmatNo
Safety ratingNot rated (no compliance review on record)
USDOT number addedJan 26, 2026 · 8 months ago
Last MCS-150 updateMay 18, 2026

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 ROYAL ROUTE INC

What does ROYAL ROUTE INC's operating authority allow?

MC1792888: Motor carrier (may haul regulated property for hire).

Which information about ROYAL ROUTE INC is old or missing?

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 ROYAL ROUTE INC?

Confirm the authority and insurance on the Motus record for USDOT 4524047. Call the company back on the phone number on file, (425) 309-2008, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1792888, 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 21:29 UTC.