Thanks for the feedback! Do you know which brand of eSIM esim.me provides, or are there several brands to choose from? I’m also curious in the questions @jaclaz brought up.
The UICCID numbers below are hidden intentionally for privacy.
[admin@MikroTik] > /interface/lte/esim print
Flags: A - ACTIVE
Columns: INTERFACE, NAME, SPN, UICCID
# INTERFACE NAME SPN UICCID
0 lte1 eSIM.me eSIM.me 8949xxxx9
1 A lte1 Holafly Holafly 89431xxxxx9
[admin@MikroTik] > /interface/lte/esim/activate number=0
[admin@MikroTik] > /interface/lte/esim print
Flags: A - ACTIVE
Columns: INTERFACE, NAME, SPN, UICCID
# INTERFACE NAME SPN UICCID
0 A lte1 eSIM.me eSIM.me 8949xxxx9
1 lte1 Holafly Holafly 89431xxxxx9
What you see above is that the physical card has two eSIMs. The first eSIM from eSIM.me was present on the card since the very begining. This is how I got the physical card. I don’t know its purpose yet and because of that I did not try to delete it. I am keeping it for now. Making eSIM number 0 active disables my Holafy Internet connection immediately, meaning that the switching between the eSIMs is instant and makes the LTE interface disconnect and then try to reconnect via the other eSIM that doesn’t not have subscription.
[admin@MikroTik] > /interface/lte/esim refresh-profile-list
interface:
[admin@MikroTik] > /interface/lte/esim refresh-profile-list interface=lte1
[admin@MikroTik] >
I am not sure if the result of the refresh is successful.
Finally, I believe this output might be interesting for you. I just deleted my Holafly eSIM from the physical card.
[admin@MikroTik] > /interface/lte/esim/print
Flags: A - ACTIVE
Columns: INTERFACE, NAME, SPN, UICCID, NICKNAME
# INTERFACE NAME SPN UICCID NICKNAME
0 lte1 eSIM.me eSIM.me 8949xxxx9
1 A lte1 Holafly Holafly 89431xxxxx9
[admin@MikroTik] > /interface/lte/esim/delete
number
[admin@MikroTik] > /interface/lte/esim/delete number=1
Profile not in disabled state
[admin@MikroTik] > /interface/lte/esim/deactivate number=1
[admin@MikroTik] > /interface/lte/esim/delete number=1
[admin@MikroTik] > /interface/lte/esim refresh-profile-list
interface: lte1
eSIM command in progress
[admin@MikroTik] > /interface/lte/esim/print
Columns: INTERFACE, NAME, SPN, UICCID
# INTERFACE NAME SPN UICCID
0 lte1 eSIM.me eSIM.me 8949xxxx9
On tha packaging of the eSIM physical cards, it is written:
TelcoVillage GmbH, Hennigsdorfer Str. 126, 13503 Berlin, Germany
I assume this is the vendor (the brand) of the cards.
This physical eSIM card has 5 slots for profiles. There is an option to unlock more slots via the mobile app of eSIM with payment.
I think it is the actual company behind the esim.me “brand”, esim.me is listed among their “products”:
https://www.telcovillage.com/
https://www.telcovillage.com/#esim
And on esim.me site:
https://esim.me/about_us
so we can say that esim.me and telcovillage are one and the same.
Interestingly, the “single” type has two sub-types, and it can store up to 2 profiles OR up to 5, the “multi” has 3 sub-types, up to 5, up to 7 and up to10, and the “omni” only one, up to 15 devices:
https://esim.me/eSIM-for-your-smartphone//#20132-manage_on_a_single_device-up_to_2_esim_profiles
You should be able to identify the chip manufacturer using the EID (eUICC Identifier). I’m curious if the EID is somehow included in the eSIM profile itself and can be viewed by ROS, or if there are any other ways to retrieve that information perhaps using AT commands?
This is a good point — it does need internet first to reach the MNO’s server to activate. Docs do say that in roundabout way - that might be missed in testing:
connectivity to eSIM SIM profile provider SM-DP+ provisioning server during provisioning and deletion of SIM profiles on eSIM chip (for connectivity, can use another eSIM profile or another WAN interface)
Now perhaps the working internet requirement is at least one possible reason why there have been mixed results with eSIM.me/etc in other threads… If there is no internet, that also be another reason why a “physical eSIM” might not work.
Now there is still an open question on the role of the specific modem hardware has on whether eSIM might work, @ortazebra suggested above with 9esim that the FG621-EA did not work and R11e-LTE6 allowed only switching existing profiles:
FWIW @ros44’s eSIM.me(/esim.bg) success was with the Quectel EG18-EA modem that in the Chateau LTE18.
Still I’d like to think MikroTik tested at least one of these physical eSIM… so be good to know what one(s) their testing with. And I suspect they might know which existing modems will work…
RouterOS LPA supports:
AT modems which firmware supports SIM low access commands (AT+CCHO; AT+CCHC; AT+CGLA)
MBIM modems which supports SIM low level access service in its firmware (UUID_SERVICE_MS_UICC)
…so MT certainly they must know which of their current shipping modem supports either one of those.
I have asked MT support for recommendation of physical SIM provider/vendor and they replied they cannot recommend anyone. I assumed not recommending a vendor is political decision and I didn’t ask anything else.
There is a list of this modems from MikroTik
These modems do not have eSIM built in. Requires an external eSIM chip. For example, a physical eSIM card (eSIM in a standard SIM form factor).
https://help.mikrotik.com/docs/spaces/ROS/pages/30146563/LTE#LTE-ModemeSIMmanagementsupporttable
Ok 
, the Mikrotik list completed with device name and model and (cleverly?) coloured (how it should have been made).
The LTAP mini and the KNOT don’t have an evident way to check the modem model or it is not present in Mikroptik’s original table, if anyone know, please post the info and I will update my table.
EDIT: Attachments updated with the info from ortazebra and optio (thanks). The modem in the Knot remains “unclassified” at the moment.
esim_modems.xls (17.5 KB)
LTAP mini lte kit (2024) - EC200A-EU
LTAP mini lte kit - R11e-LTE
R11e-LTE6 is also used in HAP AC3 LTE6 KIT
Chateau LTE12 (RBD53G-5HacD2HnD-TC&EG12-EA) has EG12-EA, also should be supported.
There is cAP LTE12 ax duplicate row, maybe is meant to be instead one of them.
Hi everyone,
Just a quick warning for those using eSIM profiles.
I had successfully provisioned several eSIM profiles using a physical eSIM card in my Chateau LTE12 (old version) running 7.19.3. Everything worked fine. Then I removed one of the profiles by (while another profile was active):
/interface/lte/esim delete <list_number_of_print_command>
After that, I tried to re-provision the same profile, but it failed with this error:
status: Server didn't authenticate eSIM (status: Failed, subject code: 8.2, reason code: 1.2, subject identifier: Profile, message: Bad profile state [expected=Released or DeleteSucceeded or Error_DownloadFailed or Downloaded] [actual=Installed_Enabled])
It seems like the delete command removed the profile locally, but did not properly de-register it with the provider. Now the profile is in a bad state and can’t be re-downloaded.
Be careful: Deleting a profile like this might break it permanently. This could be a bug or maybe some extra step is missing. I’ve already contacted MikroTik support (SUP-194541) to find out.
If anyone has seen this before or knows a workaround, please share!
Thanks
Edit: CLI screenshot for evidence.
Edit: Needless to say, I also tried to provision the “removed eSIM profile” on a Android device. It fails saying “eSIM is used on another device”.
Can you specify which one you used (or if there were several) ?
Looking for an option for SXT LTE6 and AX Lite LTE.
Do you mean the physical card or the providers?
Physical card please.
I suppose you need to add the first profile using some app then ?
It is this one from EIOTCLUB: https://www.eiotclub.com/products/physical-esim-card
There was a profile pre-activated when I received the card. I used the card-reader to provision a second profile. Then I put the card in the device and used ROS to add a third profile. So I had 3 profiles in total. I removed the profile I had initially added using the card-reader (profile 2). Delete was successful. But wanted to add it again and now I am stuck because esim profile server denies it. I do not know why it was even removed without de-registering on the server. Mikrortik docs are clear:
- connectivity to eSIM SIM profile provider SM-DP+ provisioning server during provisioning and deletion of SIM profiles on eSIM chip (for connectivity, can use another eSIM profile or another WAN interface)
So the DELETE should only be possible when the connectivity to the esim profile server is available and can be done. But apparently it was deleted without ever notifying the esim profile server. What a pity. I did not expect being beta-tester when Mikrotik is already doing heavy marketing on the eSIM functionality. I thought it is solid/stable already.
OK, US based but they also have presence in Europe via Germany.
Will check it out. Thanks for the info.
I actually bought it from here: https://www.amazon.de/dp/B0DJ8MQN3V
Just noticed, it’s even cheaper on Amazon then via their website 