Since January 2025, the FMCSA has removed 79 or more Electronic Logging Devices from the registered list -- and the pace accelerated through 2026 with batch revocations of 9, 10, 12, and 14 devices at a time. If any of your buses run a revoked device on day 61 after the revocation date, the driver is placed out of service at roadside, cited under 49 CFR 395.8(a)(1), and your CSA score takes the hit. The 60-day grace window sounds generous until you factor in 2-3 weeks of hardware procurement and 3-4 weeks of installation and driver training. This is the practical 2026 walkthrough of the revocation list, the 5-step monthly check every bus carrier should run, and the replacement timeline that keeps buses on the road. See BusCMMS track ELD devices per bus → book a 20-min demo.
FMCSA ELD Revocation List Guide for Bus Companies
The 60-day countdown, the batch-revocation history through 2026, and the monthly check that keeps drivers on the road.
"We will continue to take decisive enforcement action to ensure that only compliant, reliable devices are used on our nation's roadways." — FMCSA Administrator Derek Barrs, 2026
The 60-Day Countdown Clock
Grace period sounds long. It isn't. Here is what actually happens in 60 days.
FMCSA's industry-wide notice sets the replacement deadline at exactly 60 days from the revocation publication date. During those 60 days, the agency authorizes two backup options: paper Records of Duty Status (RODS) or compliant logging software. Safety officials at roadside inspections during the grace period are encouraged not to cite drivers under 49 CFR 395.8(a)(1) or 395.22(a), and they may request paper logs or use the revoked ELD's display as reference. Miss day 61 and the enforcement posture flips entirely -- the driver is placed out of service, the citation lands, and the CSA record takes the hit.
Revocation Published
Notice sent industry-wideFMCSA emails motor carriers. Device appears on Revoked Devices list at fmcsa.dot.gov/registration/eld. Grace window begins.
Order Replacement
ACT-BY DATEOrder replacement hardware. Procurement is 2-3 weeks normal, longer during batch revocations. Fleets that wait past day 15 hit the deadline dangerously close.
Install + Train
Fleet-wide rolloutPhysical installation across every bus, driver training on the new interface, HOS log migration. Typical window: 3-4 weeks for a mid-size fleet.
Grace Window Ends
HARD DEADLINEAny HOS log recorded on the revoked ELD after day 60 is a violation. Driver placed OOS at roadside per CVSA criteria. CSA record impacted.
The "30-day deadline" myth: Some forum posts and third-party articles claim FMCSA gives 30 days. That's wrong. Every 2025-2026 revocation notice from the agency has specified exactly 60 days from the revocation publication date. Always check the specific deadline FMCSA published for your device, not what a forum said.
The 60-day window is the entire budget for detection, procurement, installation, and training. See BusCMMS auto-track ELD revocation windows → book a demo.
Recent Revocation Batches: A 2026 History
These specific devices were removed. Deadlines came fast. Bus fleets running them had to pivot.
Ev ELD Inc. + others
Replace by Sep 8, 2026Ten devices removed in a single industry-wide notice. Ev ELD Inc. (formerly Evo ELD Inc.) among the affected providers.
Multi-provider batch removal
Replace by Jul 20, 2026One of the year's biggest single-day actions. FMCSA Administrator statement: "Safety is not optional, and neither is compliance."
Cross-provider action
Replace by Apr 14, 2026Nine devices removed across multiple providers in a single industry email notice.
PREMIERRIDE, DSGELOGS, STATE ELOGS
Replace by Mar 15, 2026PREMIERRIDE LOGS LLC, DSG TRACKING LLC, STATE ELOG LLC devices removed. Two separate STATE ELOGS models affected.
Year-end batch removal
Replace by Mar 1, 2026Five devices from multiple providers removed as 2025 closed out.
PSS ELD, Black Bear ELD, RT ELD Plus
Replace by Feb 7, 2026Pioneer Safety Solutions LLC, Black Bear ELD, and Rollingtrans (RT-ELITE-BLE3647) devices removed.
Batch removals are the pattern -- the era of one-device-at-a-time revocations ended in 2025. See BusCMMS check the FMCSA revoked list monthly → book a demo.
The 5-Step Monthly Registry Check
Two minutes on the official FMCSA registry. Never miss a revocation notice again.
- 1
Gather device info
PreparationProvider name, model number, firmware version, and registration ID from one bus's device or your provider's admin portal. Have it ready before opening the site.
- 2
Open the official registry
fmcsa.dot.gov/registration/eldThe only authoritative source. Third-party lists lag behind. Two lists live here: "Registered Devices" and "Revoked Devices."
- 3
Search both lists
CRITICAL · DO BOTHUse the filter or search box on the Registered Devices list AND the Revoked Devices list. Confirming presence on one is not the same as confirming absence from the other.
- 4
Match provider + model + ID
Full match requiredSame provider name is not enough -- some providers had one model revoked and others still registered. Confirm model number and ELD identifier match exactly.
- 5
Log the check date per bus
Audit trailRecord who checked, when, and the result per bus in your compliance system. Monthly cadence is the minimum -- weekly during active batch-revocation cycles.
What Happens on Day 61
Grace ends. Enforcement begins. Here is the exact cascade.
Driver Placed Out-of-Service
CVSA OOS CriteriaAt the next roadside inspection with a revoked ELD post-deadline, the driver is placed out of service immediately. The bus does not move until the situation is resolved.
Roadside Citation Issued
49 CFR 395.8(a)(1) · 395.22(a)"No record of duty status" and "Failing to use a registered ELD" citations issued to the driver. Fines vary by state and jurisdiction.
CSA Score Impact
HOS Compliance CategoryThe violation lands in the carrier's HOS Compliance category under the 2026 SMS methodology, moving the percentile toward the 80% intervention threshold.
Route Disruption + Downstream Cost
Bus stranded, passengers reroutedThe stranded bus needs recovery, passengers need rerouting, and a substitute driver has to be dispatched. Every hour is direct operational cost on top of the compliance hit.
The reversible piece
If an ELD provider corrects all identified deficiencies, FMCSA can put the device back on the Registered Devices list. This has happened for a small number of revoked devices. But you cannot count on it -- once your device is revoked, plan for full replacement rather than waiting for reinstatement.
The Real Replacement Timeline
60 days sounds like plenty. Then you look at the actual weeks needed.
Detection + Decision
Registry check finds revocation. Fleet team reviews shortlist of compliant replacements. Vendor calls.
Hardware Procurement
Purchase orders, vendor lead times, shipping. Normal window is 2-3 weeks. Longer during batch-revocation surges when many fleets order at once.
Install + Driver Training
Physical install across every bus. Driver training on the new device interface. HOS log migration. Backup device pairing.
Cutover + Verify
Final cutover per bus, verification that logs are flowing to the new device, driver re-check. Buffer for anything that goes wrong.
The math
Total realistic window: 7-9 weeks for a 40-bus fleet. The 60-day FMCSA deadline is 8.5 weeks. That is the entire buffer. A fleet that catches the revocation on day 10 instead of day 0 has already lost more than 10 percent of its runway. A fleet that catches it on day 30 is functionally past the point of safe procurement -- paper logs become the fallback and driver time becomes the cost.
Where BusCMMS Fits Your ELD Program
Six ways the revocation notice never catches you at day 45.
ELD Registry Per Bus
Provider, model, ELD identifier, firmware version, and installation date tracked per VIN. One-click reference during the monthly registry check.
Monthly Registry Check Reminder
Auto-fires on the 1st of every month. Weekly cadence during active batch-revocation cycles. Log check date, checker, and result per bus.
60-Day Countdown Workflow
When a device is flagged revoked, a workflow fires with day-15 order deadline, week-5 install target, and day-60 hard cutoff.
Replacement Procurement Log
Purchase orders, vendor status, ship dates, and per-bus install completion tracked. Nothing falls between spreadsheets during the crunch.
Driver Training Attestation
Every driver signs off on the new ELD interface training with date and device pairing. Audit-ready trail if the roadside inspection asks.
HOS Log Continuity
Old device HOS records archived per bus + driver at cutover. New device flow verified. No lost logs during migration.
Our motorcoach fleet was running one of the revoked devices in the May 2026 batch. We only found out because a driver's roadside inspector mentioned it -- 34 days into the 60-day window. Procurement took us 22 days because half the industry was ordering at once. We ran paper RODS across 28 buses for the last two weeks before the deadline, and it was chaos. Moved every ELD registration into BusCMMS the following month with monthly registry checks per bus. Two revocations since. Both caught within 48 hours of the FMCSA notice.
Monthly ELD check due? The registry review takes two minutes. Sign up free and log your fleet's ELDs →
Frequently Asked Questions
How many days do I have to replace a revoked ELD?
Exactly 60 days from the FMCSA revocation publication date. Every 2025-2026 revocation notice from FMCSA has specified 60 days -- the "30-day" figure sometimes cited in forum posts and third-party articles is incorrect and can cause fleets to make premature or panicked decisions. During the 60-day grace window, drivers can continue using the revoked device as a display reference, and FMCSA explicitly authorizes two backup options: paper Records of Duty Status (RODS) or compliant logging software. Safety officials at roadside inspections during the grace period are encouraged not to cite drivers under 49 CFR 395.8(a)(1) or 395.22(a). Starting on day 61, enforcement flips entirely: any HOS log recorded on the revoked device is a violation, the driver is placed out of service per CVSA criteria, and the citation lands.
Where do I check the FMCSA revoked ELD list?
The only authoritative source is the official FMCSA registry at fmcsa.dot.gov/registration/eld. Third-party lists and blog posts always lag behind by days or weeks. Two lists live on the page: "Registered Devices" and "Revoked Devices" -- check both, because confirming presence on the registered list is not the same as confirming absence from the revoked list. The check itself takes about two minutes if you have your device information ready: provider name, model number, ELD identifier, and firmware version. Same provider name is not enough for confirmation -- some providers had one model revoked while other models remained registered, so match model number and ELD identifier exactly. Bus fleets should run this check on a monthly cadence at minimum, weekly during active batch-revocation cycles.
How many ELDs has FMCSA revoked since 2025?
FMCSA has removed more than 79 devices from the registered list since January 2025, and the pace has accelerated through 2026. Recent batches include 10 devices on July 10, 2026 (Ev ELD Inc. and others, deadline September 8), 12 devices on May 20, 2026 (deadline July 20), 9 devices on February 14, 2026 (deadline April 14), 4 devices on January 13, 2026 (PREMIERRIDE LOGS LLC, DSG TRACKING LLC, STATE ELOG LLC, deadline March 15), 5 devices on December 30, 2025 (deadline March 1, 2026), and 3 devices on December 8, 2025 (PSS ELD, Black Bear ELD, RT ELD Plus, deadline February 7, 2026). Every removal is because the device failed to meet minimum requirements under 49 CFR Appendix A to Subpart B of Part 395. FMCSA Administrator Derek Barrs has publicly stated the agency will continue removing non-compliant devices to protect the integrity of the ELD program.
What happens if my bus driver runs a revoked ELD past the deadline?
A four-step enforcement cascade. First, at the next roadside inspection with a revoked ELD post-deadline, the driver is placed out of service per CVSA OOS Criteria -- the bus does not move until the situation is resolved. Second, roadside citations are issued under 49 CFR 395.8(a)(1) "No record of duty status" and 49 CFR 395.22(a) "Failing to use a registered ELD." Third, the violation lands in the carrier's HOS Compliance category under the 2026 SMS methodology, moving the CSA percentile toward the 80th percentile intervention threshold. Fourth, direct operational cost -- stranded bus recovery, passenger rerouting, substitute driver dispatch, and downtime pile on top of the compliance hit. In rare cases FMCSA reinstates a device if the provider fixes deficiencies, but fleets should never plan on that outcome -- once a device is revoked, plan for full replacement.
How does BusCMMS help bus fleets track ELD compliance?
BusCMMS tracks every ELD per bus with provider name, model number, ELD identifier, firmware version, and installation date. A monthly registry-check reminder fires on the 1st of every month (weekly during active batch-revocation cycles) with the check date, checker name, and result logged per bus. When a device is flagged revoked, a 60-day countdown workflow fires with the day-15 order deadline, week-5 install target, and day-60 hard cutoff -- so nothing falls between spreadsheets during the crunch. Purchase orders, vendor shipping status, and per-bus install completion track in one place. Driver training on the new device gets signature attestation with date and device pairing. Old-device HOS records archive at cutover so no logs are lost during migration. One 28-bus Mid-Atlantic motorcoach operator reported catching two subsequent revocation notices within 48 hours of FMCSA publication after moving ELD tracking into BusCMMS -- compared to the 34-day delay that had cost them 22 chaotic days of paper RODS on their previous revocation event.
