Lavergne, Tennessee trucking carriers
57 FMCSA-registered carriers
57
Carriers
56
Total inspections
6
Total crashes
2
HazMat carriers
Lavergne out-of-service rates vs. national average
How to shortlist carriers recorded in Lavergne
The installed records report 154 power units across 57 carrier identities. 12 have recorded inspections; 45 have none in this dataset. No inspections is not a clean safety record.
Record imports range from 2026-03-13 to 2026-10-18. These are our import dates, not the dates of each underlying inspection or a live authority check. The city is the reported physical address; crashes and inspections can occur elsewhere.
- Open the exact USDOT profile; match its legal name and MC number with your counterparty documents.
- Check the operating status, source dates and available public insurance filings. A fleet count or low inspection rate does not establish suitability.
- Confirm current authority and insurance against the official records and the insurer before contracting.
The OOS figures below are unweighted means of available carrier rates, not a pooled inspection rate. The national reference was checked on 4 August 2026; populations and periods can differ. Do not interpret the difference as a city safety ranking.
Carrier verification checklist · Public example report · Official FMCSA identity lookup
Trucking in Lavergne, Tennessee
Lavergne, Tennessee has 57 imported motor-carrier records with this physical city address, reporting 223 drivers. This is a record count, not a count of currently hiring or authorised local businesses. 12 carriers have inspection records, totaling 56 inspections. The average driver out-of-service rate is 10.8%, above the national average of 6.7%. Carriers in Lavergne have 6 crashes on record. 2 carriers handle hazardous materials.
Before the rate confirmation
Vetting a Lavergne carrier?
Open the carrier profile for the raw FMCSA-derived record, or request a documented review. Your first complete verification report is free. Broker Pro is available when your team needs shared history, saved carriers, and ongoing monitoring.