NOTE: The list below is for informational purposes only and describes hardware tested by our device experts. emnify does not require your device to be certified by emnify. All local certification requirements continue to apply (CE, FCC, PTCRB etc.) and please check this certification with the device vendor.
Various modems are being tested continuously with our SIM cards for their basic connectivity and IMSI switch interoperability. Below is a summary list of results to be used as a quick look up. This page is being updated with the new test results.
The modems are tested on the evaluation boards from their own manufacturers. The tests are performed in Berlin, Germany. Due to unavailability of 3G networks in Germany, 3G connectivity tests cannot be done.
| Manufacturer | Model | Supported RATs | Firmware Version | RATs Tested Successfully | RATs Not Tested | IMSI Switch Test | Test Date | emnify Test SIM Version | Notes |
| Huawei | ME909u-521 | 4G Cat.3, 3G, 2G | 11.0.1.1(H697SP4C983) | 4G Cat.3, 2G | 3G | Successful | 2022-12 | v7 | |
| MeiGLink | SLM320-E | 4G Cat.1bis, 2G | SLM320PE_TK_V51_U12 | 4G Cat.1bis, 2G | Successful | 2024-10 | v7 | There was an issue with IMSI switch operation with MeiG firmware SLM320PE_TK_V51_U09. However MeiG has fixed this issue in their following firmware:
| |
| Murata | LBAD0XX1SC-DM | 4G Cat.M1, 4G Cat.NB1 | RK_03_00_00_00_02751_001 | 4G Cat.M1 | 4G Cat.NB1 | N/A | 2023-08 | iSIM | |
| Nordic Semiconductor | nRF9160 | 4G Cat.M1, 4G Cat.NB1 | mfw_nrf9160_1.2.3 | 4G Cat.M1, 4G Cat.NB1 | Successful with LTE-M | 2023-04 | v7 | ||
| Quectel | BG95-M3 | 4G Cat.M1, 4G Cat.NB2, 2G | BG95M3LAR02A04 | 4G Cat.M1, 4G Cat.NB2, 2G | Successful | 2023-01 | v7 | ||
| Quectel | BG96 | 4G Cat.M1, 4G Cat.NB1, 2G | BG96MAR02A07M1G | 4G Cat.M1, 4G Cat.NB1, 2G | Successful with LTE-M | 2022-12 | v7 | ||
| Quectel | EC21-E | 4G Cat.1, 3G, 2G | EC21EFAR06A04M4G | 4G Cat.1, 2G | 3G | Successful | 2022-12 | v7 | |
| Quectel | EC21-EC | 4G Cat.1, 3G, 2G | EC21ECGAR06A04M1G | 4G Cat.1, 2G | 3G | Successful | 2022-12 | v7 | |
| Quectel | EC25-EU | 4G Cat.4, 3G, 2G | EC25EUGAR08A01M4G | 4G Cat.4, 2G | 3G | Successful | 2022-12 | v7 | |
| Quectel | EG21-G | 4G Cat.1, 3G, 2G | EG21GGBR07A11M1G | 4G Cat.1, 2G | 3G | Successful | 2022-12 | v7 | |
| Quectel | EG25-G | 4G Cat.4, 3G, 2G | EG25GGBR07A08M2G | 4G Cat.4, 2G | 3G | Successful | 2022-12 | v7 | |
| Quectel | EG91-EX | 4G Cat.1, 3G, 2G | 4G Cat.1 | 2G, 3G | Successful | 2022-12 | v7 | ||
| Quectel | EG915U-EU | 4G Cat.1, 2G | EG915UEUABR03A01M08_01.004.01.001 | 4G Cat.1, 2G | Unsuccessful | 2024-11 | v7 | There was an issue with this firmware version of the Quectel module. Under limited service conditions, TERMINAL RESPONSE to the STK command of PROVIDE LOCAL INFORMATION contained the result as Normal Service ("Command performed successfully"), whereas we would expect to see "Command performed successfully, limited service". This was fixed by Quectel in their later firmware version. We tested again with the below firmware and it works successfully: EG915UEUABR03A01M08_01.213.01.213 | |
| Quectel | RG255C-GL | 5G Redcap Sub-6 SA, 4G Cat.4 | RG255CGLABR01A04M4G | 4G Cat.4 | 5G Redcap Sub-6 SA | Successful | 2025-12 | v7.20 | Although successful under normal conditions, the EF LOCI file on SIM was not deleted by the module when network blocking was applied, which prevented the IMSI switch. This may cause IMSI switch delays in scenarios where network blocking is used on emnify portal. |
| Sierra Wireless | EM7455 | 4G Cat.6, 3G | SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30 | 4G Cat.6 | 3G | Successful | 2023-03 | v7 | |
| SIMCom | A7672E-FASE | 4G Cat.1, 2G | A011B09A7672M7_F | 4G Cat.1, 2G | Successful | 2025-07 | v7.7 | ||
| SIMCom | A7682E | 4G Cat.1, 2G | A011B01A7682M7 | 4G Cat.1 | 2G | Successful | 2024-06 | v7.7 | |
| SIMCom | SIM7000G | 4G Cat.M1, 4G Cat.NB1, 2G | 1529B01SIM7000G | 4G Cat.M1, 2G | 4G Cat.NB1 | Successful with LTE-M | 2023-03 | v7 | Could not connect it to NB-IoT networks in presence of LTE-M networks even with manual attach. Besides, this modem does not function well in the absence of LTE-M and NB-IoT networks where 2G GSM is available only. This is due to its "better RAT search" functionality with the priority list as CAT-M > NB-IOT > GSM. This functionality cannot be switched off and it causes unhealthy network connections. |
| sSIMCom | SIM7020E | 4G Cat.NB1 | 1752B01SIM7020E | 4G Cat.NB1 | Unsuccessful | 2023-01 | v7 | Works well with manual operator selection (AT+COPS=1). Automatic mode AT+COPS=0 is not efficient.
Note: Use SIMCom specific AT command to configure the APN instead of 3GPP standard AT+CGDCONT: AT*MCGDEFCONT="IP","em" | |
| SIMCom | SIM7020G | 4G Cat.NB1 | 1910B06SIM7020G | 4G Cat.NB1 | Unsuccessful | 2023-01 | v7 | No IMSI switch.
Note: Use SIMCom specific AT command to configure the APN instead of 3GPP standard AT+CGDCONT: AT*MCGDEFCONT="IP","em" | |
| SIMCom | SIM7070G | 4G Cat.M1, 4G Cat.NB1, 2G | 1951B07SIM7070 | 4G Cat.M1, 2G | 4G Cat.NB1 | Successful | 2023-01 | v7 | NB-IoT does not make any connection (even in manual attach mode) despite NB-IoT networks are visible in the network search. |
| SIMCom | SIM7080G | 4G Cat.M1, 4G Cat.NB1 | 1951B05SIM7080 | 4G Cat.M1, 4G Cat.NB1 | Successful with LTE-M | 2023-01 | v7 | NB-IoT connection was possible with manual attach. | |
| SIMCom | SIM7500E | 4G Cat.1, 3G, 2G | LE11B06SIM7500M21 | 4G Cat.1, 2G | 3G | Successful | 2022-12 | v7 | |
| SIMCom | SIM7600G | 4G Cat.1, 3G, 2G | LE20B02SIM7600M21-A | 4G Cat.1, 2G | 3G | Successful | 2022-12 | v7 | |
| SIMCom | SIM7600G-H | 4G Cat.4, 3G, 2G | LE20B02SIM7600M22_200312 | 4G Cat.4, 2G | 3G | Successful | 2022-12 | v7 | New test in 2025-06 with v7.10: IMSI switch can be problematic after a sucessfull 2G connection. The LOCI file is not updated quickly. This prevents an IMSI switch occuring for some time. It becomes necessary to wait for the module to make a CS attachment attempt so that LOCI is cleared. The device firmware may be needed to clear xLOCI files for a faster action. |
| SIMCom | SIM7672G | 4G Cat.1bis | 2308B01SIM7672M5A_230201 | 4G Cat.1bis | Unsuccessful | 2024-01 | v7 | No attachment in automatic mode. Could only achieve connection with manual attach. No IMSI switch could be achieved.Not compatible with v7 eUICC SIM. | |
| Telit (Gemalto Cinterion) | BGS2-W | 2G | N/A | N/A | N/A | 2023-09 | v7 | The modem is not compliant with 3GPP Release 6 which is the minimum requirement for eUICC SIMs. This modem is 3GPP release 99 compliant. | |
| Telit (Gemalto Cinterion) | BGS2-W | 2G | 2G | Successful | 2023-09 | v5 | |||
| Telit | GL865-DUAL V3.1 | 2G | N/A | N/A | N/A | 2023-08 | v7 | The modem is not compliant with 3GPP Release 6 which is the minimum requirement for eUICC SIMs. This modem is 3GPP Release 4 compliant. | |
| Telit | GL865-DUAL V3.1 | 2G | 2G | Unsuccessful | 2023-08 | v5 | Network attachment and PDP sessions work well but IMSI switch does not work. | ||
| Telit | LE910C4-WWXD | 4G Cat.4, 3G, 2G | M0F.603006 | 4G Cat.4, 2G | 3G | Successful | 2025-06 | v7.10 | |
| Telit | LE910C1-WWXD | 4G Cat.1, 3G, 2G | M0F.403006 | 4G Cat.1, 2G | 3G | Successful | 2025-06 | v7.10 | |
| Teltonika | TM2500 | 2G | 2G | Successful | 2022-12 | v7 | |||
| u-blox | LEXI-R10801D | 4G Cat.1bis | 01.05 | 4G Cat.1bis | Successful | 2025-01 | v7.10 | Also tested firmware version 01.07.A01.00Hi Luksa with SIM v7.20 in 2025-11 and the result is successful. | |
| u-blox | SARA-R410M-02B | 4G Cat.M1, 4G Cat.NB1 | 1141A | To be tested. | |||||
| u-blox | SARA-R412M-02B | 4G Cat.M1, 4G Cat.NB1, 2G | M0.12.00 [Dec 04 2020 16:05:31] | 4G Cat.M1, 2G | 4G Cat.NB1 | Successful | 2023-03 | v7 | Could not connect to NB-IoT even in manual mode. |
Comments
0 comments
Please sign in to leave a comment.