RYDER TRUCK RENTAL INC

DBA RYDER

USDOT 16130 · Coral Gables, FL

Not for-hire

Quick answers

Is RYDER TRUCK RENTAL INC (USDOT 16130) allowed to operate?
Yes. As of September 10, 2026, FMCSA's live record shows RYDER TRUCK RENTAL INC (USDOT 16130) is allowed to operate.
What is RYDER TRUCK RENTAL INC's FMCSA safety rating?
RYDER TRUCK RENTAL INC holds a Satisfactory FMCSA safety rating (rated February 4, 1987). This is FMCSA's official rating — one of Satisfactory, Conditional, or Unsatisfactory.
What is RYDER TRUCK RENTAL INC's USDOT number?
RYDER TRUCK RENTAL INC is registered under USDOT 16130, based in Coral Gables, FL. FMCSA classifies it as a private (not-for-hire) carrier.
How large is RYDER TRUCK RENTAL INC's fleet?
RYDER TRUCK RENTAL INC reports 59,883 power units and 328 drivers in its FMCSA record in Coral Gables, FL.

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

Operating snapshot

59,883Power units (fleet size)
328Drivers reported
52Years since registration
718MAnnual miles reported (2024)
Coral Gables, FLHome base
2,575Inspections (24 mo)

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

53
Moderate
HaulReport estimate · highest estimated percentile
Hours-of-Service Compliance is this carrier's highest reconstructed BASIC percentile at the 53.0th percentile among 694 safety-event peers. Across 3 rated categories, 2 are 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

Ryder Truck Rental Inc, operating as Ryder, is a private property carrier based in Coral Gables, Florida, with 59,883 power units and 328 drivers. In 2024, the carrier logged 717.5 million miles. Vehicle out-of-service inspections occurred at 10.6%, below the snapshot benchmark of 21.2%, while driver out-of-service rates were 2.0%, below the snapshot benchmark of 5.2%. HaulReport-estimated percentiles show controlled substances at 2.9 (low band) and vehicle maintenance at 39.3 (low band), with hours-of-service compliance at 53.0 (moderate band)—an independent estimate, not an official FMCSA or CSA score.

HaulReport interpretation — automatically generated from the public FMCSA data below and our percentile estimates, and checked against those source figures.

Estimated BASIC percentiles

Controlled Substances / AlcoholLow
2.9 pctl · CI 08
BASIC measure: 0.01Insp. w/ violation: 5Peer group: 102
Hours-of-Service ComplianceModerate
53.0 pctl · CI 4858
BASIC measure: 0.14Insp. w/ violation: 2,558Peer group: 694
Vehicle MaintenanceLow
39.3 pctl · CI 3444
BASIC measure: 2.20Insp. w/ violation: 1,625Peer group: 497

Out-of-service rates

Vehicle OOS10.6%below the 21.2% snapshot benchmark · 1,625 inspections
Driver OOS2.0%below the 5.2% snapshot benchmark · 2,558 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 October 2027
Next biennial update dueOctober 2027
Recurring update monthOctober, odd-numbered years
Last MCS-150 update on fileJune 6, 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

Safety

  • Rating: Satisfactory (as of February 4, 1987)
  • Driver out-of-service rate: 1.9%
  • Vehicle out-of-service rate: 11.4%
  • Hazmat out-of-service rate: 1.9%

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

Change history & operating authority

  1. September 14, 2026New crash report published in the FMCSA crash file
  2. September 14, 2026New crash report published in the FMCSA crash file
  3. September 12, 2026New crash report published in the FMCSA crash file
  4. September 12, 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 7, 2026New crash report published in the FMCSA crash file
  8. September 5, 2026New crash report published in the FMCSA crash file
  9. September 4, 2026New crash report published in the FMCSA crash file
  10. September 3, 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. August 31, 2026New crash report published in the FMCSA crash file
  14. August 30, 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 30, 2026New crash report published in the FMCSA crash file
  18. August 30, 2026New crash report published in the FMCSA crash file
  19. August 29, 2026New crash report published in the FMCSA crash file
  20. August 29, 2026New crash report published in the FMCSA crash file
  21. August 28, 2026New crash report published in the FMCSA crash file
  22. August 28, 2026New crash report published in the FMCSA crash file
  23. August 28, 2026New crash report published in the FMCSA crash file
  24. August 28, 2026New crash report published in the FMCSA crash file
  25. August 27, 2026New crash report published in the FMCSA crash file
  26. August 24, 2026New crash report published in the FMCSA crash file
  27. August 24, 2026New crash report published in the FMCSA crash file
  28. August 23, 2026New crash report published in the FMCSA crash file
  29. August 23, 2026New crash report published in the FMCSA crash file
  30. August 23, 2026New crash report published in the FMCSA crash file
  31. August 23, 2026New crash report published in the FMCSA crash file
  32. August 23, 2026New crash report published in the FMCSA crash file
  33. August 21, 2026New crash report published in the FMCSA crash file
  34. August 21, 2026New crash report published in the FMCSA crash file
  35. August 21, 2026New crash report published in the FMCSA crash file
  36. August 21, 2026New crash report published in the FMCSA crash file
  37. August 17, 2026New crash report published in the FMCSA crash file
  38. August 17, 2026New crash report published in the FMCSA crash file
  39. August 15, 2026New crash report published in the FMCSA crash file
  40. August 15, 2026New crash report published in the FMCSA crash file
  41. August 15, 2026New crash report published in the FMCSA crash file
  42. August 12, 2026New crash report published in the FMCSA crash file
  43. August 10, 2026New crash report published in the FMCSA crash file
  44. August 10, 2026New crash report published in the FMCSA crash file
  45. August 10, 2026New crash report published in the FMCSA crash file
  46. August 9, 2026New crash report published in the FMCSA crash file
  47. August 9, 2026New crash report published in the FMCSA crash file
  48. August 8, 2026New crash report published in the FMCSA crash file
  49. August 8, 2026New crash report published in the FMCSA crash file
  50. August 8, 2026New crash report published in the FMCSA crash file
  51. August 7, 2026New crash report published in the FMCSA crash file
  52. August 7, 2026New crash report published in the FMCSA crash file
  53. August 6, 2026New crash report published in the FMCSA crash file
  54. August 6, 2026New crash report published in the FMCSA crash file
  55. August 6, 2026New crash report published in the FMCSA crash file
  56. August 6, 2026New crash report published in the FMCSA crash file
  57. August 6, 2026New crash report published in the FMCSA crash file
  58. August 3, 2026New crash report published in the FMCSA crash file
  59. August 2, 2026New crash report published in the FMCSA crash file
  60. July 30, 2026Crash report removed from the FMCSA crash file
  61. July 30, 2026New crash report published in the FMCSA crash file
  62. July 30, 2026New crash report published in the FMCSA crash file
  63. July 27, 2026New crash report published in the FMCSA crash file
  64. July 25, 2026New crash report published in the FMCSA crash file
  65. July 24, 2026New crash report published in the FMCSA crash file
  66. July 24, 2026New crash report published in the FMCSA crash file
  67. July 24, 2026New crash report published in the FMCSA crash file
  68. July 24, 2026New crash report published in the FMCSA crash file
  69. July 23, 2026New crash report published in the FMCSA crash file
  70. July 23, 2026New crash report published in the FMCSA crash file
  71. July 20, 2026New crash report published in the FMCSA crash file
  72. July 19, 2026New crash report published in the FMCSA crash file
  73. July 19, 2026New crash report published in the FMCSA crash file
  74. July 18, 2026New crash report published in the FMCSA crash file
  75. July 18, 2026New crash report published in the FMCSA crash file
  76. July 16, 2026New crash report published in the FMCSA crash file
  77. July 15, 2026New crash report published in the FMCSA crash file
  78. July 13, 2026New crash report published in the FMCSA crash file
  79. July 13, 2026New crash report published in the FMCSA crash file
  80. July 11, 2026New crash report published in the FMCSA crash file
  81. July 11, 2026New crash report published in the FMCSA crash file
  82. July 11, 2026New crash report published in the FMCSA crash file
  83. July 10, 2026New crash report published in the FMCSA crash file
  84. July 10, 2026New crash report published in the FMCSA crash file
  85. July 5, 2026New crash report published in the FMCSA crash file
  86. July 4, 2026New crash report published in the FMCSA crash file
  87. July 4, 2026New crash report published in the FMCSA crash file
  88. July 3, 2026New crash report published in the FMCSA crash file
  89. July 3, 2026New crash report published in the FMCSA crash file
  90. July 2, 2026New crash report published in the FMCSA crash file
  91. July 2, 2026New crash report published in the FMCSA crash file
  92. June 29, 2026New crash report published in the FMCSA crash file
  93. June 28, 2026New crash report published in the FMCSA crash file
  94. June 27, 2026New crash report published in the FMCSA crash file
  95. June 27, 2026New crash report published in the FMCSA crash file
  96. June 27, 2026New crash report published in the FMCSA crash file
  97. June 26, 2026New crash report published in the FMCSA crash file
  98. June 26, 2026New crash report published in the FMCSA crash file
  99. June 25, 2026New crash report published in the FMCSA crash file
  100. June 22, 2026New crash report published in the FMCSA crash file
  101. June 22, 2026phone changed— → 7862471987
  102. June 21, 2026New crash report published in the FMCSA crash file
  103. June 20, 2026New crash report published in the FMCSA crash file
  104. June 20, 2026New crash report published in the FMCSA crash file
  105. June 20, 2026New crash report published in the FMCSA crash file
  106. June 20, 2026New crash report published in the FMCSA crash file
  107. June 19, 2026New crash report published in the FMCSA crash file
  108. June 19, 2026New crash report published in the FMCSA crash file
  109. June 19, 2026New crash report published in the FMCSA crash file
  110. June 19, 2026New crash report published in the FMCSA crash file
  111. June 18, 2026New crash report published in the FMCSA crash file
  112. June 18, 2026New crash report published in the FMCSA crash file
  113. June 16, 2026New crash report published in the FMCSA crash file
  114. June 16, 2026New crash report published in the FMCSA crash file
  115. June 15, 2026New crash report published in the FMCSA crash file
  116. June 15, 2026New crash report published in the FMCSA crash file
  117. June 15, 2026New crash report published in the FMCSA crash file
  118. June 13, 2026New crash report published in the FMCSA crash file
  119. June 13, 2026New crash report published in the FMCSA crash file
  120. 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 number16130
Legal nameRYDER TRUCK RENTAL INC
Doing business asRYDER
LocationCORAL GABLES, FL
Operating classificationNot for-hire (per FMCSA census)
Power units (fleet size)59,883
Drivers328
Reported annual mileage717,535,263 (reported for 2024)
FMCSA registered1974 (~52 years)
Last MCS-150 updateJune 6, 2025
Next MCS-150 update dueOctober 2027
Inspections (trailing 24 mo)2,575
Published BASIC measures3

State reference data: Truck-crash statistics for Florida — state-wide totals for all carriers registered in Florida, 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/16130/