Your Top Questions About NTN NB-IoT, Answered

On September 4, 2025, we co-hosted a webinar on NTN NB-IoT Uncovered: What It Is, What It Isn’t, and Where It Wins with Viasat. This is emerging technology with a great deal of promise, and we had a large audience, with an accordingly large number of questions! We’ve collated these questions into several topics in this blog post, which we will keep updated as the roadmap progresses.

Quick Links:

Pricing and Licensing

What is the expected cost of hardware (e.g., modem, antenna)?

Hardware pricing varies widely depending on the capabilities your project requires. Some modules are designed purely as basic modems to connect to NTN NB-IoT networks and are relatively inexpensive, but they only provide connectivity.

Products like RockBLOCK RTU are far more than just a connection point. In addition to NTN NB-IoT access, they include:

• Edge processing to handle data locally and reduce transmission frequency (saving airtime and battery life).
• Configurable sensor reading and alerting, so you can trigger transmissions only when thresholds are met.
• A plug-and-play design, enabling faster deployment and simpler integration with cloud platforms like Cloudloop.

Because of this added functionality, RockBLOCK RTU and similar devices sit at a different price point than a simple dongle, but they often reduce overall project costs by lowering airtime usage, extending battery life, and minimizing field maintenance.

In short, the “right” hardware investment depends on whether you need just connectivity or a complete field-ready solution that simplifies operations and scales with your project.

How does NTN NB-IoT communication cost compare to terrestrial NB-IoT and proprietary satellite solutions?

Satellite NB-IoT is designed for very small, infrequent data transmissions, such as a few tens of bytes per hour or day. Because of the complexity of delivering data over satellites, the cost per kilobyte is much higher than for terrestrial NB-IoT, which benefits from existing cellular infrastructure and is inexpensive for high volume, high frequency data.

For ultra-low data applications, Satellite NB-IoT promises to be more affordable than traditional proprietary satellite services, which are built for higher throughput, always-on connections. However, as data usage rises beyond roughly a few dozen kilobytes per month per device, the cost of satellite NB-IoT can quickly become more expensive, making other satellite solutions like Iridium Messaging Transport, or Viasat IoT Nano, more economical.

In short:

• Terrestrial NB-IoT is the lowest cost option, but only works where there is cellular coverage.
• Satellite NB-IoT fills the gap where coverage is missing, offering lower costs than legacy satellite services for small, infrequent messages.
• Proprietary satellite solutions remain the best fit for higher data volumes, real time control, or truly global coverage.

Power Consumption

What are the expected power requirements for receiving and sending messages?

Final power profiles are still being confirmed, but early testing of devices shows very low power consumption, similar to cellular NB-IoT at the edge of coverage. Typical behavior is short, high-power bursts during transmission, with the device in deep sleep the rest of the time.

• Transmit (TX): Brief bursts at a few hundred milliamps for fractions of a second per message.
• Receive (RX): Much lower current for very short listening periods.
• Deep Sleep: Extremely low standby current between events.

For ultra-low data use cases – such as one small (50-byte) message per day – battery life can be measured in years. Even at one message per hour, multi-year operation is still realistic with careful design, especially when payloads remain small, retries are minimized, and devices have a clear view of the sky.

Tip: Use short, infrequent messages and Non-IP Data Delivery (NIDD) where possible to maximize battery life.

Data & Protocols

What counts as “small data volumes,” and how is data usage calculated (uplink vs downlink)?

For NTN NB-IoT, small data volumes generally mean 30-50 KB per month per device. This roughly equates to one small message (around 50 bytes) every hour, making it ideal for applications like periodic sensor readings or exception-based reporting.

Data usage is calculated as the total of both uplink and downlink traffic, combined.

• Uplink: Data sent from the device, such as sensor readings or alerts.
• Downlink: Data sent to the device, such as configuration updates or acknowledgements.

In most deployments, uplink traffic dominates, with only small amounts of downlink data needed. However, frequent acknowledgements or commands sent to the device will eat into the monthly budget, so it’s best to minimize downlink usage wherever possible.

Rule of thumb: If your device sends a 50-byte message hourly, you’ll be close to the 30-50 KB/month sweet spot, but adding regular downlink messages or retries can quickly push usage higher.

Are message acknowledgements supported, and do they consume billable data?

In principle, acknowledgements are supported, but whether they’re available depends on the hardware and how it’s configured. Some devices, such as RockBLOCK RTU, can be programmed to generate acknowledgements, while others may not include this functionality out of the box.

Because an acknowledgement is just another downlink message, it does consume data and counts toward the device’s total monthly allowance (both uplink and downlink combined).

Frequent use of acknowledgements can quickly increase data consumption, so it’s best to:

• Use them sparingly, such as for critical alerts where confirmation is essential.
• Keep acknowledgement messages very small to stay within the <30 KB/month sweet spot.
• Design systems so that most reporting is uplink-only, with acknowledgements reserved for exceptions or configuration updates.

Tip: If battery life and cost are key priorities, minimize acknowledgements and focus on efficient, uplink-driven workflows.

Will the service work at sea or in harsh environmental conditions (e.g., offshore, deserts, extreme temperatures)?

The service is certainly capable of this, but today it isn’t available for maritime applications (see above). Instead, explore message-based solutions like Viasat IoT Nano or Iridium Messaging Transport (IMT) for an economical alternative that has truly global coverage.

How does NTN NB-IoT compare to proprietary satellite services like Iridium SBD?

NTN NB-IoT is designed for very small, infrequent data transmissions, such as tens of bytes per hour, making it a cost effective choice for applications like remote monitoring, tracking, and metering where usage stays below roughly 30-50 KB per month. It currently offers regional coverage rather than true global reach and has moderate latency, typically tens of seconds, which is acceptable for periodic updates but not for time-critical control.

Message-based proprietary services such as Iridium SBD share some similarities with NTN NB-IoT, as they also focus on small, discrete payloads and are well-suited for remote reporting. However, SBD offers truly global coverage, including oceans and polar regions, and has both lower latency and higher throughput, making it more robust for mobile or mission-critical assets.

In contrast, IP-based satellite services like Viasat IoT Pro or Iridium Certus 100 provide a continuous, always-on connection. This enables real time command and control, streaming data, and more complex integrations, something neither NTN NB-IoT nor SBD can deliver. These services are typically more expensive and consume more power, but they are essential for applications such as autonomous systems, live video feeds, or continuous telemetry.

In summary:

• NTN NB-IoT is ideal for ultra-low power, ultra-low data needs.
• Message-based services like SBD are better for mobile or global small data applications.
• IP-based services are the only option for real-time control and high throughput use cases.

How does network selection work when both terrestrial and satellite networks are available?

Most devices come with lowest-cost routing built in, so will use terrestrial when available, switching to satellite when cellular drops out, and allow control over when the device will attempt a satellite connection once cellular is not available.

Can we manage NTN NB-IoT devices and integrate using existing patterns in Cloudloop?

Yes. NTN NB-IoT devices can be fully managed and monitored within Cloudloop, alongside other satellite IoT devices, giving you a single, unified view of your entire deployment.

Through Cloudloop Data, information from NTN NB-IoT devices is automatically reformatted and standardized, so it can be delivered to a wide range of destinations, including cloud platforms, analytics tools, and third-party systems. This means you can continue using your existing integration patterns and workflows, with no need to rebuild or redesign your backend systems to handle NTN NB-IoT traffic.

Examples of integration destinations include:

• AWS IoT Core
• Azure IoT Hub
• Google Cloud IoT
• REST APIs and custom endpoints
• Webhooks for custom workflows.

Because Cloudloop is network- and protocol-agnostic, it works seamlessly with both standards-based NB-IoT devices and proprietary satellite solutions, making it ideal for organizations running mixed technologies.

How suitable is NTN NB-IoT for UAVs, HAPs, or other mobile applications?

NTN NB-IoT is not well suited for UAVs (Uncrewed Aerial Vehicles), HAPs (High-Altitude Platforms), or similar mobile applications. These platforms typically require an always-on, real time connection for tasks such as command and control, continuous telemetry, or video streaming.

NTN NB-IoT, by design, is optimized for tiny, infrequent data messages with latency measured in tens of seconds. This makes it perfect for periodic reporting, such as a water level sensor or asset tracker, but completely unsuited for dynamic, fast moving systems where constant situational awareness is required.

For UAVs, HAPs, and other highly mobile assets, you’ll need an IP-based satellite connection, which provides a continuous, reliable data link. Good options include:

• Iridium Certus 100 – a truly global service for mobile platforms, ideal for command and control and small data streams.
• Viasat IoT Pro – an IP-based L-band solution offering higher throughput for more complex or data-intensive applications.
• Hardware like the RockREMOTE Mini OEM, designed specifically for integrating into UAVs or other custom mobile systems.

Could NTN NB-IoT replace or compete with services like Iridium or Starlink in the future?

In the foreseeable future, the answer is no. NTN NB-IoT and proprietary satellite systems are designed to solve different problems and will coexist for many years to come. Viasat continues to invest in its IoT Nano and IoT Pro services, and similarly, Iridium is planning to launch its own NTN NB-IoT service in the next two years and that will exist alongside their SBD, IMT and Certus 100 IoT services.

NTN NB-IoT opens up entirely new classes of applications that were previously cost prohibitive, thanks to its lower device and connectivity costs. However, this comes with trade-offs in data volumes, latency, coverage, and potential congestion. It is, at its core, a cellular standard adapted for satellite use, whereas proprietary systems were purpose-built for satellite, optimized to send data as efficiently as possible while conserving power and bandwidth.

Looking further ahead, in the mid-2030s, we expect to see the introduction of NTN NR (New Radio), a next-generation standard that supports much higher data rates and lower latency. While this could significantly change the landscape, it’s too early to predict what the commercial proposition will look like or whether it could compete directly with purpose-built satellite services.

Ultimately, the physics of satellite communication impose unavoidable constraints: it will always be more expensive and power hungry than terrestrial cellular networks, which limits its use to specific scenarios. The deciding factor over the next decade will not just be technology, but commercial dynamics – which service delivers the best mix of coverage, performance, and cost for a given application.

Antenna Requirements

Does NTN NB-IoT require direct line of sight, and how does it perform under partial obstruction (e.g., forest canopy)?

Viasat’s NTN NB-IoT service requires direct line of sight between the antenna and the satellite because it operates on GEO (geostationary) satellites. If the signal is obstructed, for example, by buildings, thick forest canopy, or even certain vehicle structures, performance will degrade significantly, and the connection may fail altogether. This makes careful antenna placement essential.

By comparison, services using LEO (Low Earth Orbit) satellites, such as Iridium’s forthcoming NB-IoT service, NTN Direct, are a little more forgiving. With multiple satellites constantly moving across the sky, a general “clear view of the sky” is sufficient, and temporary obstructions are less of a problem.

For practical guidance, see our article: What Does a Clear View of the Sky Mean? This explains how to evaluate your site and position antennas for reliable connectivity, whether you’re dealing with trees, rooftops, or industrial environments.

In Summary

NTN NB-IoT opens up exciting new possibilities for connecting devices in remote or hard-to-reach locations, enabling low cost, low power communication at a scale that was previously out of reach for many industries. However, like any technology, it has its strengths and limitations. It’s best suited to small, infrequent transmissions where latency is acceptable, and less suited to real time or high data volume applications.

If you’d like to explore NTN NB-IoT further, we’ve included some recommended resources below. And if you still have questions or want to discuss how NTN NB-IoT might fit into your specific project, please get in touch using the form at the bottom of this page, or email hello@groundcontrol.com; our team will be happy to help.