Industry News
Quick Verdict
There is an unannounced Whoop device in the public regulatory record. It is called the WM50, it is filed under FCC ID 2AJ2X-WM50, Whoop Inc. is the applicant, the FCC describes it as a "Sensor Device," and it was granted on May 15, 2026. Gadgets & Wearables, which first surfaced it, also found a Singapore IMDA registration dated June 10, 2026. More than three months after clearance, nothing has shipped.
Here is the honest reading. What the filings prove is narrow: Whoop has a Bluetooth-only sensor device certified and waiting. The genuinely interesting detail, which we confirmed by pulling both records side by side, is that the WM50 lists only the 2402 to 2480 MHz band, while the WS50 record behind Whoop's current hardware carries a second grant at 13.56 MHz. That is NFC, and it is gone. Everything past that point, including the product's name, price, positioning, launch date, and what the missing NFC means, is inference. Whoop has said nothing. Treat the rest of the coverage accordingly, including ours.
What Is Actually in the FCC Record
An FCC equipment authorization is not a product announcement. It is a certification that a radio meets emissions rules, filed because a company cannot legally sell a transmitting device in the US without one. Companies file for hardware that ships, hardware that slips, and hardware that gets cancelled outright.
What the WM50 record contains: Whoop Inc. as grantee, "Sensor Device" as the equipment description, a grant dated May 15, 2026, an operating range of 2402 to 2480 MHz, and an equipment class of "Digital Transmission System," which is the standard classification for Bluetooth. The exhibit list is the usual set for a body-worn wireless device: a BLE test report, antenna gain specifications, SAR reports with their supporting probe and dipole certificates, test setup photos, a block diagram, schematics, and operational descriptions. The device also uses an e-label rather than a printed FCC ID, which is normal for something too small to print on.
What the record does not contain: a product name, a price, a release date, or any description of what the sensor senses.
The Detail That Stands Out
Gadgets & Wearables flagged that the WM50 drops the "NFC Tag Reader transmitter subsystem and its associated supporting circuitry" relative to its predecessor. We checked that against the primary records rather than taking it secondhand, and the radio inventories do differ:
| Field | WS50 (2AJ2X-WS50) | WM50 (2AJ2X-WM50) |
|---|---|---|
| Applicant | Whoop Inc. | Whoop Inc. |
| Equipment description | Sensor Device | Sensor Device |
| Grant date | May 8, 2025 | May 15, 2026 |
| Bluetooth band | 2402 to 2480 MHz | 2402 to 2480 MHz |
| 13.56 MHz radio (NFC) | Present, as a Part 15 low power communication device grant | Not listed |
| Status | Shipping hardware | Unreleased as of August 28, 2026 |
Gadgets & Wearables identifies the WS50 as the platform behind the Whoop MG, and its grant date sits a year ahead of the WM50's. So the comparison is fair: same applicant, same equipment description, one fewer radio.
What the Missing NFC Probably Is Not
The obvious guess is contactless payments, and that is almost certainly wrong in both directions. Removing a radio is a cost and space decision, not a feature announcement, and an NFC tag reader is not a payment element anyway.
Gadgets & Wearables offers the more plausible theory, and labels it as a theory: the NFC subsystem may handle communication between the sensor and the battery pack, which would make its removal a sign of a different power or accessory architecture rather than a lost user-facing feature. That is a reasonable read. It is also unverified. Whoop has not commented on the WM50 at all, and no filing document available to the public explains what the 13.56 MHz radio in the WS50 was doing. Anyone telling you confidently what the missing NFC means is extrapolating from a frequency table.
When We Will Actually Know More
There is a date on the calendar. Whoop requested both short term and long term confidentiality on the WM50 filing, which is routine for unreleased hardware, and the FCC record shows the confidential documents becoming available on November 11, 2026. That is when the internal and external photos and the schematics are scheduled to open up.
Photos are the useful part. They show form factor, sensor layout, and battery arrangement, which is far more informative than a frequency list. If the WM50 has not launched by then, November 11 is the next real information event. If Whoop launches it sooner, the photos become moot.
How to Read Filings Without Getting Burned
Regulatory sightings are the most reliable rumor source in wearables, and they are still not a roadmap. The filing is proof that hardware exists and was engineered to a shippable standard. It is not proof of a launch, and the gap between grant and release runs from weeks to never.
The practical advice: do not defer a purchase on this. A device with no name, no price, no date, and sealed photos is not a thing you can wait for responsibly. If you are weighing Whoop right now, decide on the hardware and the subscription that exist today. Our guides on Whoop 5 vs Whoop MG, whether Whoop is still worth it in 2026, and why people look for alternatives cover the actual decision. Whoop's recent move into lab testing is a better signal about company direction than any filing.
Where Vora Fits
This story is a small argument for not tying your health history to one company's hardware cycle. A new device may be coming, or the WM50 may never ship. Either way, your sleep, strain, and recovery history should outlive the decision.
Vora reads from Apple Health and Health Connect, so the data your wearable writes there stays usable if you switch devices or brands. Being straight about the Whoop case: Whoop's own app is where Whoop's recovery and strain scores live, and how much of that reaches Apple Health or Health Connect depends on what Whoop chooses to write out, which is a limit on the Whoop side, not something any third party can fix. Check integrations for what actually syncs before you assume a metric will follow you. The general principle holds regardless: data in an open health store survives your next upgrade, and data in a vendor silo does not.