HaulReportIndependent US motor-carrier records directory, built on public FMCSA data.

ESTES EXPRESS LINES

DBA ESTES

USDOT 121018 · Richmond, VA

Authorized for-hireAuthority activeHazmat

Quick answers

Is ESTES EXPRESS LINES (USDOT 121018) allowed to operate?
Yes. As of September 15, 2026, FMCSA's live record shows ESTES EXPRESS LINES (USDOT 121018) is allowed to operate.
Does ESTES EXPRESS LINES have active operating authority?
Yes. FMCSA's live records show active common, contract, and broker operating authority for ESTES EXPRESS LINES (MC97275) as of September 15, 2026.
Does ESTES EXPRESS LINES have insurance on file with FMCSA?
Yes. FMCSA shows liability (BIPD) coverage of $5,000,000 and a surety bond of $75,000 on file for ESTES EXPRESS LINES as of September 15, 2026. "On file" reflects the filed amounts, not confirmation of active coverage.
What is ESTES EXPRESS LINES's FMCSA safety rating?
ESTES EXPRESS LINES holds a Satisfactory FMCSA safety rating (rated January 29, 2001). This is FMCSA's official rating — one of Satisfactory, Conditional, or Unsatisfactory.
What is ESTES EXPRESS LINES's USDOT and MC number?
ESTES EXPRESS LINES is registered under USDOT 121018 and operating authority MC97275, based in Richmond, VA. FMCSA classifies it as an authorized for-hire carrier that is registered to haul hazardous materials.
How large is ESTES EXPRESS LINES's fleet?
ESTES EXPRESS LINES reports 9,805 power units and 8,821 drivers in its FMCSA record in Richmond, VA.

Answers reflect the public FMCSA record as of September 15, 2026; figures can change at any time.

Operating snapshot

9,805Power units (fleet size)
8,821Drivers reported
52Years since registration
621MAnnual miles reported (2024)
Richmond, VAHome base
4,651Inspections (24 mo)

Public FMCSA census & inspection records · as of 2026-06-06

54
Moderate
HaulReport estimate · highest estimated percentile
Vehicle Maintenance is this carrier's highest reconstructed BASIC percentile at the 53.6th percentile among 497 safety-event peers. Across 2 rated categories, 1 is estimated Low. Higher percentile = more inspection-violation activity recorded relative to peers. An independent estimate, not an official FMCSA or CSA score.
Estimated from public FMCSA data · updated 2026-06-08 · How we calculate this

ESTES EXPRESS LINES is a for-hire motor carrier based in Richmond, VA, operating 9,805 power units and 8,821 drivers, and has been registered with FMCSA for about 52 years (since 1974). It is flagged as a hazardous-materials carrier in the FMCSA census. In this public FMCSA inspection snapshot it has 4,651 recorded inspections, with a vehicle out-of-service rate of 16.6% (below the 21.2% snapshot benchmark) and a driver out-of-service rate of 0.7% (below the 5.2% benchmark). HaulReport's highest reconstructed BASIC percentile for this carrier is Vehicle Maintenance at the 53.6th percentile (estimated band: Moderate), ranked among 497 safety-event peers — an independent estimate, not an official FMCSA or CSA score.

HaulReport interpretation — auto-generated from the public FMCSA data below and our percentile estimates.

Estimated BASIC percentiles

Hours-of-Service ComplianceLow
34.8 pctl · CI 30–40
BASIC measure: 0.09Insp. w/ violation: 4,622Peer group: 694
Vehicle MaintenanceModerate
53.6 pctl · CI 49–59
BASIC measure: 2.79Insp. w/ violation: 2,775Peer group: 497

Out-of-service rates

Vehicle OOS16.6%below the 21.2% snapshot benchmark · 2,775 inspections
Driver OOS0.7%below the 5.2% snapshot benchmark · 4,622 inspections

Out-of-service rate = inspections resulting in an out-of-service order ÷ inspections. The benchmark is the inspection-weighted rate across this FMCSA snapshot — not an official national average. Rates are shown only with at least 5 inspections.

MCS-150 biennial update

Due August 2027
Next biennial update dueAugust 2027
Recurring update monthAugust, odd-numbered years
Last MCS-150 update on fileJuly 29, 2025

FMCSA sets each carrier's biennial update month from the last two digits of the USDOT number (last digit → month, second-to-last digit → odd/even year) — it is required even when nothing has changed. This is a schedule derived from the public rule, not a compliance determination. Verify and file on FMCSA · Deadline calculator

Live FMCSA status

Allowed to operate

Operating authority

  • Common: Active
  • Contract: Active
  • Broker: Active
  • Docket: MC97275
  • Authorized for property, broker

Insurance on file

  • Liability (BIPD): $5,000,000
  • Surety bond: $75,000

Safety

  • Rating: Satisfactory (as of January 29, 2001)
  • Driver out-of-service rate: 0.9%
  • Vehicle out-of-service rate: 16.4%
  • Hazmat out-of-service rate: 3.1%

Live read from FMCSA's QCMobile system on September 15, 2026. Insurance figures are FMCSA "on file" amounts, not confirmation of current coverage; values can change at any time. FMCSA QCMobile

Insurance on file

Liability (BIPD)Surety bond
2 filings on file — show details
  • Public liability (BIPD)LIBERTY MUTUAL INSURANCE CO.Form 82 · effective 2025-05-01
  • Surety bondFIDELITY & DEPOSIT CO. OF MARYLANDForm 84 · effective 2013-10-01

Insurance filings on record in FMCSA's Licensing & Insurance (L&I) system (active or pending per the source dataset), as of 2026-06-08. Dollar figures are the maximum limit recorded on the filing, not confirmation of current coverage, and this is not a recommendation; filings can change or lapse at any time and may not reflect today's status. Confirm current coverage directly with FMCSA. Verify on FMCSA L&I

Change history & operating authority

Active

FMCSA operating authority is currently active for this carrier.

  1. September 14, 2026New crash report published in the FMCSA crash file
  2. September 13, 2026New crash report published in the FMCSA crash file
  3. September 13, 2026New crash report published in the FMCSA crash file
  4. September 13, 2026New crash report published in the FMCSA crash file
  5. September 12, 2026New crash report published in the FMCSA crash file
  6. September 11, 2026New crash report published in the FMCSA crash file
  7. September 11, 2026New crash report published in the FMCSA crash file
  8. September 7, 2026New crash report published in the FMCSA crash file
  9. September 6, 2026New crash report published in the FMCSA crash file
  10. September 6, 2026New crash report published in the FMCSA crash file
  11. September 3, 2026New crash report published in the FMCSA crash file
  12. September 3, 2026New crash report published in the FMCSA crash file
  13. September 3, 2026New crash report published in the FMCSA crash file
  14. August 31, 2026New crash report published in the FMCSA crash file
  15. August 30, 2026New crash report published in the FMCSA crash file
  16. August 30, 2026New crash report published in the FMCSA crash file
  17. August 29, 2026New crash report published in the FMCSA crash file
  18. August 24, 2026New crash report published in the FMCSA crash file
  19. August 21, 2026New crash report published in the FMCSA crash file
  20. August 21, 2026New crash report published in the FMCSA crash file
  21. August 21, 2026New crash report published in the FMCSA crash file
  22. August 21, 2026New crash report published in the FMCSA crash file
  23. August 21, 2026New crash report published in the FMCSA crash file
  24. August 19, 2026New crash report published in the FMCSA crash file
  25. August 17, 2026New crash report published in the FMCSA crash file
  26. August 17, 2026New crash report published in the FMCSA crash file
  27. August 15, 2026New crash report published in the FMCSA crash file
  28. August 14, 2026New crash report published in the FMCSA crash file
  29. August 12, 2026New crash report published in the FMCSA crash file
  30. August 9, 2026New crash report published in the FMCSA crash file
  31. August 7, 2026New crash report published in the FMCSA crash file
  32. August 7, 2026New crash report published in the FMCSA crash file
  33. August 6, 2026New crash report published in the FMCSA crash file
  34. August 6, 2026New crash report published in the FMCSA crash file
  35. August 6, 2026New crash report published in the FMCSA crash file
  36. August 6, 2026New crash report published in the FMCSA crash file
  37. August 2, 2026New crash report published in the FMCSA crash file
  38. July 31, 2026New crash report published in the FMCSA crash file
  39. July 31, 2026New crash report published in the FMCSA crash file
  40. July 30, 2026New crash report published in the FMCSA crash file
  41. July 27, 2026New crash report published in the FMCSA crash file
  42. July 26, 2026New crash report published in the FMCSA crash file
  43. July 26, 2026New crash report published in the FMCSA crash file
  44. July 25, 2026New crash report published in the FMCSA crash file
  45. July 24, 2026Crash report updated — injuries: 2 → 1
  46. July 24, 2026Crash report updated — fatalities: 0 → 1
  47. July 24, 2026New crash report published in the FMCSA crash file
  48. July 18, 2026New crash report published in the FMCSA crash file
  49. July 18, 2026New crash report published in the FMCSA crash file
  50. July 16, 2026New crash report published in the FMCSA crash file
  51. July 16, 2026New crash report published in the FMCSA crash file
  52. July 14, 2026New crash report published in the FMCSA crash file
  53. July 13, 2026New crash report published in the FMCSA crash file
  54. July 13, 2026New crash report published in the FMCSA crash file
  55. July 13, 2026New crash report published in the FMCSA crash file
  56. July 13, 2026New crash report published in the FMCSA crash file
  57. July 11, 2026New crash report published in the FMCSA crash file
  58. July 10, 2026New crash report published in the FMCSA crash file
  59. July 3, 2026New crash report published in the FMCSA crash file
  60. July 3, 2026New crash report published in the FMCSA crash file
  61. July 3, 2026New crash report published in the FMCSA crash file
  62. July 2, 2026New crash report published in the FMCSA crash file
  63. June 30, 2026New crash report published in the FMCSA crash file
  64. June 29, 2026New crash report published in the FMCSA crash file
  65. June 29, 2026New crash report published in the FMCSA crash file
  66. June 28, 2026New crash report published in the FMCSA crash file
  67. June 28, 2026New crash report published in the FMCSA crash file
  68. June 26, 2026New crash report published in the FMCSA crash file
  69. June 25, 2026New crash report published in the FMCSA crash file
  70. June 25, 2026New crash report published in the FMCSA crash file
  71. June 18, 2026New crash report published in the FMCSA crash file
  72. June 18, 2026New crash report published in the FMCSA crash file
  73. June 18, 2026New crash report published in the FMCSA crash file
  74. June 17, 2026authority live record added
  75. June 16, 2026New crash report published in the FMCSA crash file
  76. June 16, 2026New crash report published in the FMCSA crash file
  77. June 15, 2026New crash report published in the FMCSA crash file
  78. June 15, 2026New crash report published in the FMCSA crash file
  79. June 15, 2026New crash report published in the FMCSA crash file
  80. June 13, 2026New crash report published in the FMCSA crash file
  81. June 13, 2026New crash report published in the FMCSA crash file
  82. June 13, 2026New crash report published in the FMCSA crash file
  83. June 13, 2026New crash report published in the FMCSA crash file
  84. June 12, 2026New crash report published in the FMCSA crash file
  85. June 12, 2026New crash report published in the FMCSA crash file
  86. June 12, 2026New crash report published in the FMCSA crash file
  87. June 12, 2026New crash report published in the FMCSA crash file

Free. One email per change — no marketing, unsubscribe anytime.

Operating-authority status is from FMCSA's licensing system; the change history is HaulReport's own append-only daily record (FMCSA does not publish change history). This is a factual record, not an official CSA score or safety rating, and can change at any time. Verify on FMCSA SAFER · See this carrier's changes in the daily FMCSA activity feed

Carrier facts (public FMCSA data)
Verbatim public facts from FMCSA datasets. Only the percentile/band/confidence figures above are HaulReport reconstructions — not official FMCSA or CSA scores.
USDOT number121018
Legal nameESTES EXPRESS LINES
Doing business asESTES
LocationRICHMOND, VA
Operating classificationAuthorized for-hire (per FMCSA census)
FMCSA operating authorityActive (per FMCSA licensing)
Hazmat carrierYes (per FMCSA census)
Power units (fleet size)9,805
Drivers8,821
Reported annual mileage620,749,705 (reported for 2024)
FMCSA registered1974 (~52 years)
Last MCS-150 updateJuly 29, 2025
Next MCS-150 update dueAugust 2027
Inspections (trailing 24 mo)4,651
Published BASIC measures2
Insurance filings (FMCSA L&I)2 on file (active/pending per source) — Public liability (BIPD), Surety bond
← Browse the HaulReport carrier directoryIs this your carrier? Request a correction or update →

State reference data: Truck-crash statistics for Virginia — state-wide totals for all carriers registered in Virginia, not specific to this carrier.

FMCSA data as of 2026-06-06 · Last synced 2026-06-08 · Method: how these percentiles are reconstructed · Canonical: https://haulreport.com/carrier/121018/