HeliumGeek Guide

Helium Mobile Offload: Speed-Test Requirements and Rollout Dates

New hotspots need 100/10 Mbps and latency of 50 ms or less for carrier submission. Active hotspot minimums increase from December 2026 through March 2027.

HeliumGeek resources / Browse FAQ

Nova's updated speed-test plan replaces the blanket pause with separate requirements for new and active hotspots. The schedule below explains what to prepare for; the HeliumGeek checks help you review your own measurements and carrier status.

Which requirements apply to my hotspot?

These changes concern Helium Mobile Hotspots. The original announcement excluded brownfield sites verified through partner agreements.

New hotspots: meet the submission requirements

New hotspots must meet at least the current Good criteria to be submitted for carrier approval: 100 Mbps download, 10 Mbps upload, and latency of 50 ms or less. All three conditions apply. Meeting them qualifies a hotspot for submission, not guaranteed approval or traffic.

Active hotspots: minimums increase in stages

Active hotspots must meet all three minimums in effect on each date to keep carrier offload. Each step replaces the previous floor:

FromDownUpLatency
December 1, 202650 Mbps5 Mbps75 ms or less
January 1, 202775 Mbps8 Mbps60 ms or less
March 1, 2027115 Mbps15 Mbps40 ms or less

Download and upload figures are minimums; latency figures are maximums. The January floor continues through February. The first listed step for active hotspots is December 1, 2026, not November 16.

March's active-hotspot floor is stricter than today's new-hotspot submission requirement. Passing 100/10 Mbps with latency of 50 ms or less is not permanent eligibility. The announcement does not separately explain how newly approved hotspots transition into the active-hotspot schedule.

Why did Nova change the rollout?

Community feedback raised concerns about applying one immediate cutoff to hotspots already carrying traffic on slower backhaul. Nova paused the new thresholds to consider that feedback, then chose staged minimums for active hotspots.

The staged plan gives deployers time to upgrade their connections while moving the network toward the carrier-grade quality its partners expect. It is time to prepare, not a permanent exemption for existing deployments. Nova also plans to review speed-test requirements during the first quarter of each year; a review does not itself mean another automatic increase.

Do location trust and heartbeats still matter?

Yes. These requirements remain in effect. The updated plan confirms that hotspots with a location trust score below 1, or that aren't sending heartbeats, will have carrier offload removed:

  • Location trust score: the November 16 clarification confirmed removal for hotspots scoring below 1. If the score is low, try a placement where the hotspot can get a clear location fix, away from metal racks, utility closets, and other enclosed spaces.
  • Heartbeats: hotspots that aren't sending heartbeats will lose carrier offload. Check that the hotspot is powered on and connected, and that the venue network or firewall isn't blocking traffic to Helium.

The update does not specify how many missed heartbeats trigger removal or how long restoration takes. A single missing app reading does not establish why a carrier stopped offloading. Improving placement or connectivity is a troubleshooting step, not a guarantee of immediate restoration.

Are these a new set of speed tests?

No. Hotspots already ran automated speed tests twice a day, measuring download, upload, and latency. These measurements determined the speed-test tier and multiplier used for Proof-of-Coverage rewards.

After PoC ended under HIP 149, the tests continued, but their results no longer determined PoC rewards. The November changes give those existing measurements a role in offload eligibility. They do not introduce a separate measurement system.

What happens if an active hotspot falls below the floor?

It will have carrier offload removed until its backhaul meets the applicable standard. Review the hotspot's measured download, upload, and latency, and plan any upgrades ahead of each step. An ISP plan's advertised speed is not a hotspot measurement.

The updated announcement does not specify the averaging window, number of failed tests that trigger removal, or restoration timing. Bringing the connection up to standard does not promise immediate approval, reactivation, or traffic.

The original announcement described weekly carrier resubmission after passing speed tests. The updated plan does not restate that process. It should not be read as a confirmed recovery timetable for this plan, or for location-trust and heartbeat removals.

What about Demand Sampling?

Demand Sampling allowed a newly onboarded or reasserted hotspot to carry unrewarded carrier traffic for about two weeks without guaranteeing paid offload. See the historical Demand Sampling guide.

The original announcement reported that new onboardings and reassertions stopped triggering sampling on November 10. It planned to end remaining sampling and require carrier location approval before offload as part of the November 16 changes. The November 17 speed-test plan does not announce a sampling change or confirm when the remaining windows ended.

What can I check in HeliumGeek?

Use the HeliumGeek mobile app to review recent hotspot activity and distinguish a change in carrier status from a change in traffic.

  1. Check recent heartbeats and Location Trust Score. Look at when the hotspot last reported a heartbeat. Inspect recent heartbeat details for the reported Location Trust Score. This is a location-verification sample, not the heartbeat availability points. A missing score is not a score of zero or proof that the hotspot passes.
  2. Open the hotspot's overview and tap a carrier. Where carrier details are available in your app version, inspect Selection, Approval, and the approval date when supplied. These are separate fields, not interchangeable labels.
  3. Compare dated speed-test results with the right requirements. For a new hotspot, use the submission criteria. For an active hotspot, start with the December 1 floor, then plan for January and March. Review download, upload, and latency together. Historical speed charts, where included in your subscription, help show whether a problem recurs.
  4. Check the carrier's actual traffic. Use the available data views to distinguish no traffic from traffic that is not rewardable. Historical Demand Sampling records still explain older traffic and should not be read as proof that sampling remains enabled.

A health color, a valid speed test, or a multiplier of 1 is not a carrier approval. Likewise, a displayed heartbeat location trust score does not establish how carrier activation is evaluated.

An Approved carrier can still be Not selected in the hotspot configuration. Approval and selection reports can update at different times, and missing approval information is not a rejection. HeliumGeek can show these observations, but they do not establish why a carrier disabled offload or when it will return.

Does this change the reward rate?

This announcement changes requirements for access to carrier offload, not the per-GB reward rate. Losing paid carrier traffic can reduce rewardable data and earnings. A hotspot with no rewardable data earns no Mobile data reward, regardless of the per-GB rate.

Subscriber allowances and other reward rules still matter. See HIP 150 and Mobile deployer rewards for the separate reward mechanics, and how live and settled data differ when comparing traffic with payouts.

How did the plan change?

  • Original announcement: planned a single 100/10 Mbps and 50 ms-or-less backhaul requirement for the November 16 rollout.
  • November 16, 2026: Nova paused the new speed-test thresholds after community feedback, while keeping location trust and heartbeat requirements in effect.
  • November 17, 2026: Nova published the revised plan: current Good criteria for new-hotspot submission and three dated floors for active hotspots.

The schedule above replaces the earlier blanket-pause guidance. We'll update this page when Nova publishes further details or changes.

Sources and related reading

Published November 14, 2026. Updated November 17, 2026, with the revised speed-test requirements and rollout dates.