YURUNOX · Cellular module selection and sourcing control
Quectel EC25 Variant Selection Guide
Choose by destination country and mobile operator first—not by the broad label “EC25.” Reject any suffix that misses a mandatory LTE band, carrier path, regulatory path, or voice requirement. Only then compare GNSS, fallback networks, SDIO and companion radios, eSIM, firmware, power, antennas, temperature, and lifecycle.
The short answer: use four rejection gates
The EC25 is a regional LTE Cat 4 family, not one worldwide radio with software-selectable geography. Quectel's March 2026 specification lists different RF bands, legacy fallback, carrier names, regulatory approvals, voice behavior, SDIO counts, companion Wi-Fi/Bluetooth interfaces, and eSIM options by suffix. A distributor's “Europe” or “North America” label is only a starting hint.
Network
Countries, operators, roaming partners, mandatory coverage and capacity bands, private bands, and network lifetime.
Approval
Exact carrier database entry, PTCRB/GCF path, national radio approvals, antenna conditions, and host obligations.
Function
Voice or data-only, GNSS option, fallback, SIM/eSIM, companion WLAN/Bluetooth, SDIO, SGMII, and audio.
Production
Full ordering code, firmware branch, PCN/EOL status, power and RF design, drivers, label, traceability, and regression tests.
Across the family, Quectel publishes LTE-FDD category limits up to 150 Mbps downlink and 50 Mbps uplink. Those are radio-category maxima, not guaranteed application throughput. Signal quality, deployed spectrum, MIMO and antenna implementation, congestion, operator policy, protocol overhead, the USB/host path, firmware, and temperature all affect field performance.
Primary references: Quectel EC25 Series Specification V3.0 and the current Quectel EC25 product page. Reviewed 28 August 2026.
The complete EC25 variant and LTE band matrix
Use this table to create a shortlist, then compare every target operator's current band and device-acceptance requirements. “Region” is Quectel's targeting label; it is not a coverage guarantee or blanket authorization.
| Variant | Published target | LTE-FDD | LTE-TDD | Important distinction |
|---|---|---|---|---|
| EC25-A | North America | B2/4/12 | — | Older, narrower set; WCDMA B2/4/5 |
| EC25-ADL | North America | B2/4/12 | — | No WCDMA, PCM, or VoLTE listed |
| EC25-V | Verizon, USA | B4/13 | — | Narrow Verizon-focused set |
| EC25-AF | North America | B2/4/5/12/13/14/66/71 | — | Voice listed; two SDIO; companion WLAN/BT path |
| EC25-AFDL | North America | B2/4/5/12/13/14/66/71 | — | Explicit data-only; two SDIO |
| EC25-AFX | North America | B2/4/5/12/13/14/66/71 | — | Voice listed; one SDIO; no WLAN/BT entry |
| EC25-AFXD | North America | B2/4/5/12/13/14/66/71 | — | Explicit data-only; one SDIO |
| EC25-AU | Latin America, Australia, New Zealand | B1/2/3/4/5/7/8/28 | B40 | WCDMA B1/2/5/8; two SDIO; WLAN/BT entry |
| EC25-AUX | Latin America, Australia, New Zealand | B1/2/3/4/5/7/8/28 | B40 | Adds WCDMA B4; one SDIO; optional external-chip eSIM path |
| EC25-J | Japan | B1/3/8/18/19/26 | B41 | Japan low bands; JATE/TELEC listed |
| EC25-EC | EMEA, Thailand | B1/3/7/8/20/28A | — | One SDIO; optional external-chip eSIM path |
| EC25-E | EMEA, South Korea, Thailand, India | B1/3/5/7/8/20 | B38/40/41 | No B28; WCDMA B5; broad published carrier list |
| EC25-EU | EMEA, Thailand | B1/3/7/8/20/28A | B38/40/41 | Two SDIO; WLAN/BT entry |
| EC25-EUX | EMEA, Thailand | B1/3/7/8/20/28A | B38/40/41 | One SDIO; no WLAN/BT entry; different carrier list |
| EC25-EM | EMEA, Southeast Asia | B1/3/5/7/8/20/28 | B38/40/41 | Broad bands; V3.0 shows no carrier certificates |
On a phone, swipe inside the table. EC25-AU and EC25-AUX have a Quectel footnote: LTE-FDD B2 does not support receive diversity. B28 and B28A are not interchangeable shorthand; confirm the deployed sub-band.
Translate the matrix into regional decisions
North America: AF family first, then separate voice and interfaces
For a new multi-operator North American product, EC25-AF, AFDL, AFX, and AFXD deserve the first review because they share B2/4/5/12/13/14/66/71. The differences are not mere firmware switches. AF and AFX list voice; AFDL and AFXD are explicit data-only models. AF/AFDL list two SDIO interfaces and companion Wi-Fi/Bluetooth application paths; AFX/AFXD list one SDIO and no such entries. Their carrier lists also differ in the V3.0 table.
EC25-A, ADL, and V can still belong in controlled legacy designs, but their narrower B2/4/12 or B4/13 coverage should be compared against B5, B14, B66, and B71 requirements. A successful attach near one laboratory tower does not prove nationwide coverage.
Australia, New Zealand, and Latin America: AU vs AUX is an interface decision too
AU and AUX share the same LTE bands and GSM fallback, while AUX adds WCDMA B4. AU lists two SDIO interfaces and companion WLAN/Bluetooth support; AUX lists one SDIO and no companion entries. AUX also lists optional eSIM support implemented in software with an external eSIM chip. Both list Telstra in the current series table, but the exact hardware/firmware entry and final-device obligations still need current confirmation.
Japan: use the local low-band and approval evidence
EC25-J adds Japan-specific FDD B18/B19/B26 and TDD B41. Quectel lists NTT DOCOMO, SoftBank, KDDI, and Rakuten, with a note that Rakuten support is data-only, plus JATE and TELEC. These entries narrow the search; they do not replace operator acceptance, antenna testing, voice-profile confirmation, or final-device conformity.
EMEA and Southeast Asia: B28, B5, TDD, and certification pull in different directions
EC25-E lacks B28 but includes WCDMA B5 and has a broad published carrier list, including South Korean operators. EU and EUX add B28A but omit WCDMA B5; they share bands but differ in SDIO/companion interfaces and carrier listings. EC25-EM combines B28 with B5 and targets EMEA/Southeast Asia, yet V3.0 shows no carrier certificates. EC25-EC includes B28A but no LTE-TDD. There is no single “best Europe version” without a country/operator matrix.
Coverage is a network-and-antenna result, not a suffix label
Low-frequency bands often support wide-area or indoor coverage, while higher-frequency capacity bands can matter in dense deployments. The host antenna must cover every enabled band with suitable efficiency and isolation inside the final enclosure. Carrier aggregation is not the subject here; the EC25 selection gate is whether the exact variant and host can meet the intended service.
A practical screening score is supported mandatory bands divided by total mandatory bands. If the launch requires B2, B4, B12, B13, and B71, EC25-A covers three of five, while the AF family publishes all five. That arithmetic is a shortlist aid—not field-test evidence or carrier approval.
EC25 shortlist tool: identify candidates and mandatory checks
Select the closest deployment profile. The result narrows the family; it does not certify a module, verify current orderability, or approve a final device.
Start with EC25-AFDL or EC25-AFXD
- Compare all mandatory operator bands and current carrier database entries.
- AFDL lists two SDIO interfaces and companion WLAN/Bluetooth paths; AFXD lists one SDIO and no companion entries.
- Freeze the exact ordering code, firmware, antenna conditions, and data-only profile.
Planning aid only. Verify the current Quectel documentation, carrier requirements, national approvals, and host design.
Voice, GNSS, eSIM, and companion radios are configuration gates
“VoLTE supported” is not a complete voice specification
A commercial voice device needs a non-data-only module, the intended PCM or voice-over-USB path, operator IMS profile, SIM provisioning, codecs, audio architecture, emergency-call scope where applicable, and operator acceptance. AFDL and AFXD are explicit data-only models. ADL lists no WCDMA, PCM, or VoLTE in V3.0. Other variants list optional VoLTE, which still ties the capability to the exact firmware and operator configuration.
For an industrial router, payment terminal, digital-signage player, or telemetry gateway, a data-only model may fit. For an intercom, alarm panel, elevator phone, or medical communications product, written operator and firmware evidence should be a pre-layout gate. Do not rely on circuit-switched 2G/3G fallback without a country-by-country lifetime plan.
GNSS is optional and still needs its own antenna qualification
Quectel lists optional GPS, GLONASS, BDS, Galileo, and QZSS. Verify the exact orderable module and firmware, the separate GNSS antenna path, passive or active antenna architecture, bias and current limits, filtering and ESD, cable loss, cellular-to-GNSS isolation, enclosure detuning, and privacy obligations.
“GNSS included” cannot guarantee field accuracy or time to first fix. Antenna view, interference, assistance data, constellation geometry, transmit coexistence, firmware, and mechanical placement can dominate the result.
Wi-Fi and Bluetooth entries describe companion architecture
The series table's Wi-Fi/Bluetooth entries do not mean every EC25 contains an independent WLAN/Bluetooth radio. The hardware design routes companion WLAN over SDIO and Bluetooth over UART/PCM. A migration from AF or EU to AFX, EUX, EC, or EM can therefore remove one SDIO interface or the listed companion path and force schematic and software changes.
eSIM support still requires an external eSIM chip
V3.0 lists optional eSIM on selected variants and explicitly notes that software support requires an external eSIM chip. The buyer must also define the eUICC supplier, electrical interface, provisioning platform, security ownership, operator profiles, lifecycle, and certification. Do not translate “eSIM optional” into “integrated eSIM.”
Two realistic buyer scenarios expose the decision consequences
Illustrative engineering scenario · not a reported YURUNOX customer result
A U.S. telemetry gateway must use AT&T and Verizon and needs B71 for a planned T-Mobile fallback
The older EC25-A lacks B13 and B71, and EC25-V lacks B2, B12, and B71. The AF family publishes all required B2/4/12/13/71 bands, so it survives the first gate. If the gateway is data-only, AFDL and AFXD are candidates; if its host uses a companion WLAN radio over the documented interface, AFDL's two SDIO paths and companion entries make it the stronger first investigation. The team must still verify current carrier entries, antenna coverage through B71, the exact firmware profile, and final-device testing.
Illustrative sourcing scenario · not a shipment or field-test claim
A single BOM is proposed for Germany, South Korea, Thailand, and a later Southeast Asia expansion
EC25-E brings the published European and South Korean carrier list but lacks B28. EC25-EM adds B28 and WCDMA B5 with EMEA/Southeast Asia targeting, yet V3.0 shows no carrier certificate list. The commercially lower-risk answer may be two controlled SKUs rather than one broad-band SKU: one with the required existing approvals and another qualified for the later market. That decision changes antenna validation, firmware branches, labels, ERP controls, forecasts, and certification budgets.
These scenarios are deliberately specific about the decision chain but do not claim first-hand YURUNOX testing or customer outcomes. Their purpose is to show why a regional suffix, band count, or price quote alone cannot close the selection.
Hardware and certification can overturn a correct band shortlist
| Area | Quectel baseline | Qualification action |
|---|---|---|
| Supply | 3.3–4.3 V, 3.8 V typical | Size the regulator, planes, vias, capacitors, cable path, and protection for worst-case transmit demand; measure at module pads. |
| RF burst | Hardware guide lists up to 1.8 A for the RF supply during burst transmission | Confirm the exact variant/mode and keep pad voltage above the documented minimum under production conditions. |
| Cellular RF | Main plus receive-diversity paths | Cover every enabled band; verify matching, efficiency, isolation, SAR/RF exposure where applicable, enclosure, cable, and user configurations. |
| Temperature | Operating −35°C to +75°C; extended −40°C to +85°C | Do not call the extended range a full-performance range. Test registration, RF behavior, throughput, recovery, and supply at real thermal extremes. |
| Mechanical | 29.0 × 32.0 × 2.4 mm LCC module; hardware guide documents 144 connections | Review the exact footprint, reserved pins, paste, reflow, keepout, ground, inspection, shielding, programming, and production-test access. |
| Migration | Quectel promotes compatibility with selected EC21, EC20-CE, EG25-G, EG21-G, and UC200A-GL modules | Run a pin-by-pin and function-by-function compatible-design review; a shared outline is not proof of drop-in equivalence. |
Hardware values and integration context: Quectel EC25 Series Hardware Design V2.4.
Certification is a stack, not one logo
- Module evidence.Confirm the exact hardware/firmware combination and its GCF/PTCRB, national radio, and carrier entries.
- Integration conditions.Follow antenna gain, RF exposure, separation, labeling, power, firmware, and host-use conditions attached to the authorization.
- Final host compliance.Evaluate host emissions, co-located radios, EMC, safety, RF exposure, national filings, and any operator-specific device tests.
- Change control.Reassess antenna, enclosure, module, firmware, SIM/eSIM profile, PCB, manufacturing, or use-case changes against the approved baseline.
PTCRB tells device makers to determine additional operator-specific testing for target markets, even when using a certified module. GSMA's IoT guidance separately states that the communications module should meet the target operator's requirements and that the IoT device may require GCF/PTCRB certification when the operator requires it. The FCC's module guidance includes a host-product integration guide. These sources support a layered plan, not a claim that module-level certificates always transfer unchanged.
Convert the design choice into an RFQ, AVL, and incoming plan
YURUNOX is an independent electronic-component sourcing partner; it does not manufacture Quectel modules or define their specifications. A sourcing review should preserve the manufacturer identity and expose any mismatch before a purchase is released.
- Define the deployment.Countries, operators, roaming partners, mandatory/desirable bands, expected service life, private-network use, and allowed fallback technologies.
- Freeze functionality.Voice/data-only status, GNSS, SIM/eSIM, companion WLAN/Bluetooth, SDIO count, SGMII, USB, UART, PCM/audio, drivers, and power modes.
- Request the full identity.Exact Quectel ordering code, clear label photo, hardware revision, firmware version, IMEI/TAC handling, carrier profile, manufacturing location, date code, and lot traceability.
- Collect current evidence.Series and hardware documentation revisions, certificates, current carrier database evidence, antenna/integration conditions, firmware release notes, PCNs/EOL notices, MSL/packing, and change-control procedure.
- Qualify production samples.Record module label, firmware, calibration state, SIM, profile, antenna, host revision, country, and network. One successful attach is not production qualification.
- Test failure paths.Registration, handover, weak signal, peak current, supply droop, temperature, GNSS coexistence, SMS/voice, throughput, low power, DFOTA, interrupted update, recovery, and each intended SIM/operator.
- Lock the approved baseline.Store the exact module, firmware, carrier profile, antenna, PCB, enclosure, BOM, label, manufacturing process, and regression criteria as linked—not wildcard—fields.
Prepare a reviewable EC25 requirement
Send the fields that determine the suffix
Include target countries and operators, mandatory bands, voice/data-only status, GNSS, eSIM, companion-radio and host interfaces, antennas, environment, certificates, quantity, schedule, and proposed ordering codes. Ask for a documented comparison and an exception list.
Request an EC25 sourcing review- Target operators and required bands
- Exact candidate suffixes and firmware
- Carrier/regulatory evidence required
- Host, antenna, SIM, and interface constraints
- Quantity, delivery window, and lifecycle need
Related YURUNOX resources: Quectel sourcing page · quality-assurance approach · global shipment support. These links were taken from the designated current site registry.
Frequently asked questions
Which Quectel EC25 variant is best for the United States?
The AF family is the first shortlist for broad current North American band coverage because it publishes B2/4/5/12/13/14/66/71. Choose AF or AFX when voice is required and AFDL or AFXD for explicit data-only designs, then verify the exact carrier entry, interfaces, firmware, antenna, and host certification. EC25-V is a much narrower B4/B13 Verizon-focused option.
What is the difference between EC25-AF and EC25-AFX?
They share the same LTE and WCDMA bands and both list voice support. V3.0 lists two SDIO interfaces plus companion Wi-Fi/Bluetooth application support for AF, but one SDIO and no such companion entries for AFX. Their published carrier lists also differ.
Are EC25-AFDL and EC25-AFXD only firmware versions?
No. Quectel explicitly labels both as data-only variants. Treat them as exact hardware/order configurations with their own function, interface, firmware, and certification evidence—not as a switchable mode of AF or AFX.
Does every EC25 include usable GNSS?
No. Quectel lists multi-constellation GNSS as optional. Verify the exact ordering code, firmware, constellations, antenna path, active/passive antenna design, power, coexistence, and required field performance.
Can one EC25 variant work worldwide?
Usually not with equal coverage and approvals. The family uses region-specific band sets, fallback networks, functions, and certificates. A multinational product may need multiple controlled EC25 SKUs—or a different global module architecture—plus per-country antenna, firmware, regulatory, and logistics planning.
Is an FCC- or PTCRB-certified EC25 enough for the final product?
No. Module certification can reduce work, but the host must follow the authorized integration conditions and meet applicable antenna, RF exposure, emissions, labeling, co-location, operator, and final-device requirements. Confirm the rules for the exact target market and product category.
Technical sources and review boundary
- Quectel EC25 Series LTE Standard Module Specification V3.0 — March 2026 variant, band, function, driver, power, temperature, carrier, and regulatory matrix.
- Quectel LTE EC25 Series product page — family positioning, dimensions, Cat 4 limits, optional GNSS/VoLTE, and migration context.
- Quectel EC25 Series Hardware Design V2.4 — electrical, RF, antenna, interface, mechanical, and thermal integration.
- PTCRB: Get Certified — certification flow and additional operator-specific testing.
- FCC KDB 996369 — modular-transmitter and host-integration guidance.
- GSMA Communication Module Requirements and IoT Device Requirements — target-operator, GCF/PTCRB, VoLTE, and device-level context.
Review date: 28 August 2026. Recheck exact ordering-code availability, carrier and regulatory status, local operator bands, network sunsets, firmware, antenna conditions, certification grants, document revisions, PCNs/EOL notices, and final-device obligations before approval. This guide is a decision framework, not a network, regulatory, authenticity, or component approval.