Is 3GPP NTN Worth the Cost? Breaking Down Module Premiums, LTE Fees, and Satellite Surcharges

Comparing the total cost breakdown of 3GPP non-terrestrial network satellite IoT versus traditional cellular IoT

The Promise vs. the Invoice

A single NB-IoT chipset that talks to terrestrial towers and satellites. Global coverage without proprietary lock-in. Standard 3GPP protocols all the way up. If you’ve been following the NTN announcements from Qualcomm, MediaTek, and their carrier partners, you’ve probably felt the pull. It sounds like the connectivity gap is finally closing.

Then you open a spreadsheet.

You price the module. You add the carrier subscription. You discover there’s a separate satellite airtime fee. Then a per-message surcharge. Then you realize the antenna needs to be bigger, the battery needs to be fatter, and your RF engineer just added two weeks to the certification timeline. That “standard chipset” you were promised? It costs four times more than the NB-IoT module sitting in your current BOM.

The 3GPP NTN cost story has a gap between the conference-stage pitch and the purchase order, and it’s wider than most project managers expect. While satellite connectivity solves real problems—like when your fleet tracker goes silent in cellular dead zones—the cost premium requires careful justification. This article breaks it down line by line: module, carrier, airtime, and the indirect costs nobody puts on a rate card. The goal is to help you plan with real numbers instead of slide deck optimism.

Cost Layer 1: The NTN Module Premium Is Real

Start with the component you can touch. A standard NB-IoT module (a Quectel BC66, a u-blox SARA-R4 series, or similar) runs $5 to $8 at modest volumes. These are mature, high-volume parts with years of supply chain optimization behind them.

An NTN-capable NB-IoT module is a different animal. Parts built on Qualcomm’s 212S/9205S platform or MediaTek’s MT6825 NTN chipset currently price in the $20 to $40+ range, depending on volume and supplier. That’s a 3× to 5× premium over the terrestrial equivalent.

The premium isn’t arbitrary. NTN modules need additional RF front-end components to handle satellite bands (S-band or L-band, depending on the operator). They require onboard Doppler pre-compensation and timing advance logic to account for a base station moving at 7.5 km/s in low Earth orbit. They often demand a higher-gain antenna interface. And production volumes are still a fraction of terrestrial NB-IoT, which means less cost amortization.

Vendors will tell you this gap is closing. They’re right, eventually. But “eventually” doesn’t help your BOM review next quarter.

+---------------------------+-----------------+-----------------+
| Module Type               | Typical Cost    | NTN Premium     |
+---------------------------+-----------------+-----------------+
| Standard NB-IoT           | $5 – $8         | —               |
| NTN-Capable NB-IoT        | $20 – $40+      | 3× – 5×         |
| Bluetooth LE (Hubble)     | $1 – $3         | None            |
+---------------------------+-----------------+-----------------+

If you’re deploying 5,000 units, that module premium alone adds $60,000 to $160,000 to your hardware budget before you’ve transmitted a single byte.

Cost Layer 2: Carrier and Network Subscriptions Stack Fast

Here’s where the confusion starts. “3GPP NTN” doesn’t mean free access to satellites any more than “3GPP LTE” means free access to cell towers. You still need a commercial relationship with a carrier, an MNO, or a satellite network operator, and often some combination of all three.

The ecosystem is fragmented. Skylo Technologies operates as a satellite network-as-a-service provider, partnering with terrestrial MNOs to extend their coverage via satellite. OQ Technology runs its own NB-IoT satellite constellation and sells connectivity directly. MediaTek has partnered with multiple satellite operators to enable NTN on its chipsets, each with their own commercial terms.

What does this look like on an invoice? Typical carrier subscription structures include:

  • Monthly device fee: $0.50 to $1.50 per device per month, depending on the plan tier and operator. Some plans start at $1/month minimum regardless of usage.
  • Activation fee: $3 to $10 per device, one-time.
  • Minimum commitment: 12 to 24 months. Breaking early means paying out the remainder.
  • Terrestrial + satellite bundling: Some MNOs offer combined plans, but the satellite component adds a surcharge on top of the terrestrial base rate.

For a device that reports once every few hours, that $1/month minimum is punishing. You’re paying the same fee as a device streaming data continuously. Over three years, carrier subscriptions alone can run $36 to $60 per device, more than the cost of some terrestrial NB-IoT modules and their entire three-year connectivity combined.

Cost Layer 3: Satellite Airtime Is a Separate Line Item

This is the one that catches people off guard. The carrier subscription gets you access to the network. The satellite airtime charge is what you pay to actually use it.

Satellite airtime pricing for NB-IoT NTN typically follows per-KB or per-message models. Rates vary, but current market pricing clusters around $0.01 to $0.05 per KB for low-volume IoT traffic, with some operators charging per-message minimums regardless of payload size.

Let’s do the math on a concrete example. Say your device sends 200 bytes every 6 hours: a GPS fix plus a sensor reading. That’s roughly 0.2 KB per message, 4 messages per day, 120 messages per month. At a per-message rate of $0.02 (a mid-range estimate), that’s $2.40/month in airtime alone. At $0.05 per message, not uncommon for satellite surcharges, it’s $6/month.

Over three years, satellite airtime for this modest usage pattern costs $86 to $216 per device. At the higher end, airtime alone exceeds the entire three-year TCO of a terrestrial NB-IoT deployment.

And here’s the kicker: at certain usage patterns, the satellite airtime surcharge exceeds the carrier subscription. You’re paying more for the satellite hop than for the network relationship itself.

Cost Layer 4: The Costs That Don’t Appear on Any Rate Card

Module, carrier, airtime: those are the line items you can find if you dig hard enough. But there’s a fourth cost layer that only surfaces once engineering starts building.

Antenna design. Satellite NB-IoT typically requires a higher-gain antenna than terrestrial. That means a physically larger antenna, more ground plane area, and potentially a different form factor. If you’re designing a compact tracker, this can force a complete enclosure redesign. Budget $2 to $5 extra per device in antenna and RF matching costs, plus engineering time.

Power budget. Satellite links consume significantly more energy than terrestrial. Longer transmission windows, higher power amplifier output, and retry cycles on a link with ~20ms+ round-trip delay all drain batteries faster. Expect to upsize your battery or add a solar cell, adding $2 to $5 per device.

Certification. Operating on satellite bands may require additional regulatory testing beyond standard terrestrial NB-IoT certification. Depending on target markets, this can add $10,000 to $30,000 to your program-level costs.

Firmware complexity. Hybrid terrestrial/satellite handover logic isn’t trivial. Your firmware team needs to handle network selection, fallback behavior, and potentially different power management modes. That’s engineering weeks, not engineering hours.

None of this shows up on a module datasheet or a carrier rate card. All of it hits your project budget.

Total Satellite IoT Cost: A Side-by-Side 3-Year TCO Example

Let’s put it all together. One device, reporting a 200-byte payload (GPS + sensor) every 4 hours, deployed for three years.

+----------------------------+-------------+-------------+-------------+
| Cost Component             | Terrestrial | 3GPP NTN    | Hubble      |
|                            | NB-IoT      | (Satellite) | (BLE-to-Sat)|
+----------------------------+-------------+-------------+-------------+
| Module / Chipset           | $6          | $30         | $2          |
| Antenna & RF Design        | $1          | $4          | $0.50       |
| Battery / Power Budget     | $3          | $6          | $2          |
| Carrier Subscription (3yr) | $18         | $36 – $60   | —           |
| Satellite Airtime (3yr)    | —           | $24 – $72   | Included*   |
| Activation / Setup Fees    | $2          | $5 – $10    | Minimal     |
+----------------------------+-------------+-------------+-------------+
| ESTIMATED 3-YEAR TCO       | ~$30        | ~$105 – $182| ~$15 – $30  |
+----------------------------+-------------+-------------+-------------+

* Hubble pricing based on transmit-only architecture with
  connectivity included in service model. Contact Hubble
  for current rate card details.

Read that bottom row carefully. A 3GPP NTN deployment costs roughly 3.5× to 6× what a terrestrial NB-IoT deployment costs, per device, per three years. For a 5,000-unit fleet, that’s $525,000 to $910,000 versus $150,000 for terrestrial, or potentially as low as $75,000 to $150,000 with a transmit-only architecture like Hubble’s.

The cellular IoT vs. satellite cost gap isn’t a rounding error. It’s a budget-reshaping delta that changes the ROI math on entire product lines.

Do You Actually Need Two-Way Communication?

Before you accept the 3GPP NTN cost structure, ask a harder question: does your device actually need to receive data from the satellite?

Most IoT deployments are overwhelmingly asymmetric. Data flows up: sensor readings, GPS coordinates, status pings, event alerts. The cloud ingests. Dashboards render. Alerts fire. The device’s job is to report, not to listen.

Use cases that are inherently transmit-only:

  • Asset tracking: periodic location pings
  • Environmental monitoring: temperature, humidity, air quality readings
  • Livestock tracking: GPS fixes on grazing animals
  • Soil and agriculture sensors: moisture, nutrient levels
  • Leak detection: binary alert events
  • Weather stations: periodic telemetry uploads

Bidirectional capability matters when you need remote firmware updates, command-and-control downlinks, or acknowledgment-based retry logic. Those are legitimate requirements, for some deployments.

But if 80% of your fleet only sends data up, you’re paying a bidirectional premium for a unidirectional need. That premium isn’t just the module. It’s the entire cost stack documented above.

  YOUR USE CASE NEEDS:              RECOMMENDED PATH
  ─────────────────────────────────────────────────────
  ✓ Sensor data upload only     →   Transmit-only (Hubble)
  ✓ GPS / location pings only   →   Transmit-only (Hubble)
  ✓ Remote firmware updates     →   Bidirectional (NTN)
  ✓ Command & control downlink  →   Bidirectional (NTN)
  ✓ Acknowledgment / retry      →   Bidirectional (NTN)
  ✓ Occasional config changes   →   Evaluate frequency*
  ─────────────────────────────────────────────────────
  * If config changes are rare (< monthly), consider
    handling via next terrestrial connection window.

Hubble Network: What Transmit-Only Pricing Actually Looks Like

Hubble Network takes a fundamentally different approach. Instead of adding satellite capability to a cellular chipset, Hubble enables standard Bluetooth Low Energy chips, the $1 to $3 parts already in billions of devices, to transmit directly to LEO satellites.

No NTN module premium. No carrier subscription stack. No satellite airtime surcharge layered on top of a network fee layered on top of an activation charge.

The cost advantages flow from the architecture itself:

  • Module cost: Commodity BLE chipsets at $1 to $3, not specialized NTN modules at $20 to $40+.
  • Antenna: Standard BLE antenna design. No high-gain satellite antenna required.
  • Power: BLE transmission is inherently low-power. Smaller batteries, longer life, lighter devices.
  • Connectivity: Simplified pricing without the carrier/airtime/surcharge layer cake.

The tradeoff is explicit: Hubble is transmit-only. If your use case requires downlink commands or OTA firmware updates via satellite, this isn’t the right tool. But for the majority of IoT sensing and tracking applications, transmit-only is all you need, and the cost difference is dramatic.

Build Your Own TCO Model Before You Commit

3GPP NTN is a genuine technical achievement. Standardized satellite access on a cellular protocol stack is meaningful progress for the industry. But “technically impressive” and “cost-effective for my deployment” are different conversations.

The current NTN module cost, layered with carrier subscriptions, satellite airtime surcharges, and hidden engineering costs, creates a three-year TCO that runs 3.5× to 6× higher than terrestrial NB-IoT. For cost-sensitive IoT deployments at scale, that math matters.

Before you commit to an architecture, map your actual requirements. What direction does your data flow? How often? How many bytes? Do you genuinely need downlink capability, or is that an assumption you inherited from a cellular-first mindset?

For transmit-only use cases, and there are far more of them than the industry acknowledges, Hubble Network offers a path to satellite connectivity that sidesteps the entire NTN cost stack. Run the numbers. Let the spreadsheet decide.

Hubble Network delivers satellite connectivity from a standard Bluetooth chip—no premium modules, no carrier fees, no satellite surcharges. See how it works →