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

AMAZON LOGISTICS INC

DBA PRIME

USDOT 2881058 · Seattle, WA

Authorized for-hireAuthority active

Quick answers

Is AMAZON LOGISTICS INC (USDOT 2881058) allowed to operate?
Yes. As of September 14, 2026, FMCSA's live record shows AMAZON LOGISTICS INC (USDOT 2881058) is allowed to operate.
Does AMAZON LOGISTICS INC have active operating authority?
Yes. FMCSA's live records show active common, contract, and broker operating authority for AMAZON LOGISTICS INC (MC826094) as of September 14, 2026.
Does AMAZON LOGISTICS INC have insurance on file with FMCSA?
Yes. FMCSA shows liability (BIPD) coverage of $1,000,000 and a surety bond of $75,000 on file for AMAZON LOGISTICS INC as of September 14, 2026. "On file" reflects the filed amounts, not confirmation of active coverage.
What is AMAZON LOGISTICS INC's USDOT and MC number?
AMAZON LOGISTICS INC is registered under USDOT 2881058 and operating authority MC826094, based in Seattle, WA. FMCSA classifies it as an authorized for-hire carrier.
How large is AMAZON LOGISTICS INC's fleet?
AMAZON LOGISTICS INC reports 15,259 power units and 42,486 drivers in its FMCSA record in Seattle, WA.

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

Operating snapshot

15,259Power units (fleet size)
42,486Drivers reported
10Years since registration
346MAnnual miles reported (2025)
Seattle, WAHome base
4,124Inspections (24 mo)

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

11
Low
HaulReport estimate · highest estimated percentile
Vehicle Maintenance is this carrier's highest reconstructed BASIC percentile at the 10.6th percentile among 497 safety-event peers. Across 3 rated categories, 3 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

AMAZON LOGISTICS INC is a for-hire motor carrier based in Seattle, WA, operating 15,259 power units and 42,486 drivers, and has been registered with FMCSA for about 10 years (since 2016). In this public FMCSA inspection snapshot it has 4,124 recorded inspections, with a vehicle out-of-service rate of 4.2% (below the 21.2% snapshot benchmark) and a driver out-of-service rate of 0.8% (below the 5.2% benchmark). HaulReport's highest reconstructed BASIC percentile for this carrier is Vehicle Maintenance at the 10.6th percentile (estimated band: Low), 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

Controlled Substances / AlcoholLow
7.4 pctl · CI 2–12
BASIC measure: 0.02Insp. w/ violation: 10Peer group: 102
Hours-of-Service ComplianceLow
7.9 pctl · CI 3–13
BASIC measure: 0.02Insp. w/ violation: 4,103Peer group: 694
Vehicle MaintenanceLow
10.6 pctl · CI 6–16
BASIC measure: 0.91Insp. w/ violation: 2,850Peer group: 497

Out-of-service rates

Vehicle OOS4.2%below the 21.2% snapshot benchmark · 2,850 inspections
Driver OOS0.8%below the 5.2% snapshot benchmark · 4,103 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 fileFebruary 27, 2026

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: MC826094
  • Authorized for property, broker

Insurance on file

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

Safety

  • Driver out-of-service rate: 0.9%
  • Vehicle out-of-service rate: 4.5%
  • Hazmat out-of-service rate: 0.0%

Live read from FMCSA's QCMobile system on September 14, 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

Primary liability (BIPD) — maximum limit recorded by FMCSA: $1,000,000

2 filings on file — show details
  • Public liability (BIPD) — primaryOLD REPUBLIC INSURANCE COMPANY$1,000,000 max limit · Form 91X · effective 2025-02-28
  • Surety bondLIBERTY MUTUAL INSURANCE CO.Form 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 13, 2026New crash report published in the FMCSA crash file
  2. September 11, 2026New crash report published in the FMCSA crash file
  3. September 10, 2026New crash report published in the FMCSA crash file
  4. September 7, 2026New crash report published in the FMCSA crash file
  5. September 6, 2026Crash report removed from the FMCSA crash file
  6. September 3, 2026New crash report published in the FMCSA crash file
  7. August 30, 2026New crash report published in the FMCSA crash file
  8. August 30, 2026New crash report published in the FMCSA crash file
  9. August 30, 2026New crash report published in the FMCSA crash file
  10. August 29, 2026Crash report removed from the FMCSA crash file
  11. August 29, 2026New crash report published in the FMCSA crash file
  12. August 28, 2026New crash report published in the FMCSA crash file
  13. August 28, 2026New crash report published in the FMCSA crash file
  14. August 23, 2026New crash report published in the FMCSA crash file
  15. August 23, 2026New crash report published in the FMCSA crash file
  16. August 23, 2026New crash report published in the FMCSA crash file
  17. August 23, 2026New crash report published in the FMCSA crash file
  18. August 21, 2026New crash report published in the FMCSA crash file
  19. August 21, 2026New crash report published in the FMCSA crash file
  20. August 17, 2026New crash report published in the FMCSA crash file
  21. August 17, 2026New crash report published in the FMCSA crash file
  22. August 15, 2026New crash report published in the FMCSA crash file
  23. August 15, 2026New crash report published in the FMCSA crash file
  24. August 15, 2026New crash report published in the FMCSA crash file
  25. August 15, 2026New crash report published in the FMCSA crash file
  26. August 14, 2026New crash report published in the FMCSA crash file
  27. August 12, 2026New crash report published in the FMCSA crash file
  28. August 12, 2026New crash report published in the FMCSA crash file
  29. August 10, 2026New crash report published in the FMCSA crash file
  30. August 10, 2026New crash report published in the FMCSA crash file
  31. August 10, 2026New crash report published in the FMCSA crash file
  32. August 10, 2026New crash report published in the FMCSA crash file
  33. August 8, 2026New crash report published in the FMCSA crash file
  34. August 8, 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 3, 2026New crash report published in the FMCSA crash file
  38. August 3, 2026Crash report removed from the FMCSA crash file
  39. August 2, 2026New crash report published in the FMCSA crash file
  40. August 1, 2026New crash report published in the FMCSA crash file
  41. July 31, 2026New crash report published in the FMCSA crash file
  42. July 30, 2026New crash report published in the FMCSA crash file
  43. July 30, 2026New crash report published in the FMCSA crash file
  44. July 30, 2026New crash report published in the FMCSA crash file
  45. July 27, 2026New crash report published in the FMCSA crash file
  46. July 23, 2026New crash report published in the FMCSA crash file
  47. July 23, 2026New crash report published in the FMCSA crash file
  48. July 20, 2026New crash report published in the FMCSA crash file
  49. July 19, 2026New crash report published in the FMCSA crash file
  50. July 19, 2026phone changed — — → 2065295817
  51. July 18, 2026New crash report published in the FMCSA crash file
  52. July 17, 2026New crash report published in the FMCSA crash file
  53. July 16, 2026New crash report published in the FMCSA crash file
  54. July 14, 2026New crash report published in the FMCSA crash file
  55. July 14, 2026New crash report published in the FMCSA crash file
  56. July 13, 2026New crash report published in the FMCSA crash file
  57. July 13, 2026New crash report published in the FMCSA crash file
  58. July 11, 2026New crash report published in the FMCSA crash file
  59. July 9, 2026New crash report published in the FMCSA crash file
  60. July 5, 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. July 2, 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 29, 2026New crash report published in the FMCSA crash file
  67. June 29, 2026New crash report published in the FMCSA crash file
  68. June 28, 2026New crash report published in the FMCSA crash file
  69. June 26, 2026New crash report published in the FMCSA crash file
  70. June 26, 2026New crash report published in the FMCSA crash file
  71. June 25, 2026New crash report published in the FMCSA crash file
  72. June 21, 2026New crash report published in the FMCSA crash file
  73. June 20, 2026New crash report published in the FMCSA crash file
  74. June 20, 2026New crash report published in the FMCSA crash file
  75. June 20, 2026New crash report published in the FMCSA crash file
  76. June 20, 2026New crash report published in the FMCSA crash file
  77. June 19, 2026New crash report published in the FMCSA crash file
  78. June 19, 2026New crash report published in the FMCSA crash file
  79. June 17, 2026authority live record added
  80. June 15, 2026New crash report published in the FMCSA crash file
  81. June 15, 2026New crash report published in the FMCSA crash file
  82. June 12, 2026New crash report published in the FMCSA crash file
  83. 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 number2881058
Legal nameAMAZON LOGISTICS INC
Doing business asPRIME
LocationSEATTLE, WA
Operating classificationAuthorized for-hire (per FMCSA census)
FMCSA operating authorityActive (per FMCSA licensing)
Power units (fleet size)15,259
Drivers42,486
Reported annual mileage346,075,963 (reported for 2025)
FMCSA registered2016 (~10 years)
Last MCS-150 updateFebruary 27, 2026
Next MCS-150 update dueAugust 2027
Inspections (trailing 24 mo)4,124
Published BASIC measures3
Insurance filings (FMCSA L&I)2 on file (active/pending per source) — Public liability (BIPD) — primary, Surety bond
← Browse the HaulReport carrier directoryIs this your carrier? Request a correction or update →

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