Sergey Sereda (DOT 1922006) is a Washington-based intrastate carrier headquartered in Orting, WA. As of June 6, 2026 at 6:27 PM, operating authority is active but without for-hire authority. TruckGraph has detected 1 risk signal on this carrier, including: no active insurance filing on record. TruckGraph rates this carrier "Do Not Tender" based on FMCSA compliance data, inspection history, insurance status, and network connection analysis. Last synced: June 6, 2026 at 6:27 PM.
Source: FMCSA compliance records, inspection data, crash records, insurance filings, and TruckGraph analysis. View methodology
Data sourced from FMCSA public records and TruckGraph independent analysis. This is not legal advice, not a guarantee of carrier safety, and not a compliance certification. Verify through official FMCSA sources before tendering. Last synced: .
No reviews yet — be the first to share your experience with this carrier.
Is Sergey Sereda authorized to operate?
Sergey Sereda's USDOT number is active but it does not hold operating authority for for-hire interstate operations. It may operate as a private carrier. Verify status before tendering.
What is Sergey Sereda's safety record?
Sergey Sereda does not have a substantial inspection history on record. This may indicate limited interstate operations.
How many trucks does Sergey Sereda operate?
Sergey Sereda operates 1 power units with approximately 1 drivers.
Is Sergey Sereda insured?
Insurance filing details are not available in the current dataset. Verify directly with the carrier before tendering.
Has Sergey Sereda had any risk indicators?
Sergey Sereda has a risk score of 0/100 (Monitor) with 1 active risk signal. Review the risk section above and verify independently before tendering.
What is the DOT number for Sergey Sereda?
Sergey Sereda's DOT number is 1922006. These identifiers are assigned by the FMCSA and can be used to look up this carrier in official compliance databases.
For journalists and researchers
Truck Graph data is open and citable. For press inquiries, contact our editorial team.
