
How I Test eSIMs – The TechNovice Testing Methodology
Most eSIM reviews on TechNovice are based on our own hands-on testing during actual trips. For a smaller number of comparison articles — where I have not yet completed a field test in that country — I use verified provider data and direct support inquiries instead, and I label the difference clearly in every article. Either way, I do not treat marketing claims, press releases or summaries of third-party reviews as independent evidence. In provider comparisons, official provider information is used as a primary source for plan details, prices, features and stated network partners — and is labelled as provider-supplied information rather than as my own test result. I’m Nico Dudli, founder of TechNovice, based in St. Gallen, Switzerland. I’ve tested travel eSIMs and digital tools in more than 12 countries across Europe and Asia—including extensive hands-on testing with Saily, as well as comparisons with providers like Airalo and Holafly. I document every test with the network used, the exact date, the measured speeds, and a publicly verifiable Ookla Speedtest ID.
This page explains step by step how I test, which devices and tools I use, how I verify prices and discount codes—and where the honest limitations of my methodology lie.
The Methodology at a Glance
Speed measurement
-
Ookla Speedtest (speedtest.net), every result publicly verifiable via test ID
Test setup
-
Mobile data on your own SIM disabled → Test eSIM as the only active data connection
Test equipment
-
iPhone 15 Pro (primary), MacBook Air (15″, M4, 2025) – connected via personal hotspot or tethering with the eSIM
Each test is documented
-
Location, network operator, technology (5G/LTE), download speed, upload speed, ping, packet loss, date, test ID
Test conditions
-
Real travel, multiple locations, multiple days and times of day
Practical checks
-
Video calls (Google Meet, FaceTime), streaming, navigation, hotspot usage
Price verification
-
Manually checked at checkout, verification date indicated in the item description.
Weak results
-
Will be published; not filtered out

Why This Methodology Is Important
The performance of a travel eSIM depends on the local network, your location, the time of day, signal strength, and your device setup. That’s why I don’t evaluate an eSIM provider based on a single, perfect speed test. My reviews combine measurable data, public speed test IDs, and real-world use cases such as hotspot usage, navigation, video calls, and activation immediately after landing. Here’s an example from my tests in Munich: The same location delivered 182 Mbps—and just 39 Mbps fifteen minutes earlier. Anyone who shows only a single value isn’t painting a realistic picture.
I only test the things I use myself
TechNovice clearly separates hands-on field tests from provider-verified comparison articles.
When I describe an eSIM as field-tested, I have personally used that eSIM as my mobile data connection in the destination. For example, my Portugal testing covered Lisbon, the Alentejo coast, Lagos and Sagres, while my Switzerland testing takes place in my home country, where I know the local network environment well.
I also publish provider comparisons for destinations I have not yet visited or tested with that eSIM. These articles are not presented as hands-on reviews. Instead, they are based on information I verify directly from provider websites, checkout pages and support channels, supplemented where useful by clearly labelled independent traveler reports and third-party network information.
Every such article states explicitly that no TechNovice field test has been completed. I never present provider information, traveler reports or desk research as if I had measured or experienced it myself.
Two Types of eSIM Articles:
Field-tested reviews are based on my own use in the destination and include documented measurements such as dates, locations, networks and public Speedtest IDs.
Provider-verified comparisons are used for destinations where I have not completed a field test. They are based on verified provider websites, checkout data, support inquiries and, where useful, clearly identified third-party sources such as traveler reports or network documentation.
I never present provider-supplied information or third-party reports as my own field-test results.
My Saily test data in numbers
All figures come from my own Ookla speed tests on an iPhone 15 Pro, recorded during real trips. Every individual measurement is publicly verifiable through its Speedtest ID.
Saily eSIM test base
Speed tests over Saily: 41
Period: January 2025 to July 2026
Data transferred during tests: 7.5 GB
Median download: 65.2 Mbps
Highest measured download: 515.2 Mbps
Median upload: 8.9 Mbps
Median ping: 107 ms
By connection type
5G: 13 tests, median 75.4 Mbps, peak 515.2 Mbps, median ping 58 ms
LTE: 27 tests, median 50.1 Mbps, peak 247.4 Mbps, median ping 111 ms
3G: 1 test, 6.0 Mbps, ping 47 ms
By region
Portugal: 19 tests, median 62.5 Mbps, peak 137.0 Mbps
Switzerland and border region: 15 tests, median 65.3 Mbps, peak 515.2 Mbps
France: 5 tests, median 254.7 Mbps, peak 369.3 Mbps
Vietnam: 1 test, 247.4 Mbps (Con Dao, LTE)
Thailand: 1 test, 56.5 Mbps (Koh Yao Noi, 5G)
Partner networks measured
Portugal: MEO, NOS, Vodafone Portugal, ONI Telecom, Edgoo Networks
France: Orange France, Bouygues Telecom
Switzerland and border region: Monzoon Networks, AR Informatik, Speedcom AG, Hoi Internet AG, Montafonerbahn (Austria)
Vietnam: VNPT-NET
Thailand: TrueMove H
What these numbers mean, and what they don't
The median sits well below the peak. That is not a contradiction but the reality of mobile networks: 5G in a city delivers a multiple of what LTE manages in a rural area or on a mountain. This is why I report median and peak separately instead of quoting only the best result.
These measurements show performance at a specific place and time. They are not a guarantee of nationwide coverage and no substitute for the official coverage maps of local operators.
The lowest values in the dataset come from the Sagres test described above and from a 3G fallback near the Liechtenstein border. I deliberately keep these in the dataset because they are part of real travel.
How I separate my test data
Beyond the 41 Saily measurements, my speed test archive contains further tests over Wi-Fi and over my regular Swiss SIM card. These do not feed into the Saily figures.
Here's how I run speed tests
All speed tests on TechNovice are conducted using the Ookla Speedtest app (speedtest.net). I use Ookla because each result is assigned a unique, public test ID: Anyone can look up my results on speedtest.net and verify that the numbers in my articles are accurate.
My standard procedure for eSIM speed tests:
I disable mobile data on my regular Swiss SIM card so that the test eSIM is the only active data connection.
I check which local network provider and which technology the eSIM is connected to (e.g., Salt 5G, Sunrise LTE, NOS, Vodafone Portugal, or TrueMove H).
I run the Ookla Speedtest and record the download, upload, ping, and packet loss.
I note the location, date, and time, and save the test ID.
Whenever possible, I repeat the test at the same location at a different time—and at multiple locations throughout the trip.
A single speed test doesn’t tell the whole story. Mobile performance varies depending on crowd density, time of day, and signal conditions. That’s why my reviews show multiple tests across different locations and days—not just a single best result.
Note on speed test servers: Ookla connects to the nearest available server node, which isn’t always identical to my physical test location (for example, tests in the Alpstein were run via the Gais/Buchs node). Where relevant, I’ll point this out in the article.
Example of a documented eSIM test
A typical TechNovice eSIM test includes location, local network, connection type, date, Ookla test ID, download speed, upload speed, ping, and notes from the field. Here’s a real-life example from my test in Portugal:
Location: Lagos, Portugal (Algarve)
Network: MEO
Connection: LTE
Date: June 24, 2026, 10:28 a.m.
Ookla Test ID: 7126788543
Download / Upload: 137.03 Mbps / 24.28 Mbps
Ping: 111 ms
Practical Use: Google Maps, WhatsApp, hotspot, and video calls worked reliably
My Test Devices
I'm testing with the devices I actually travel with:
iPhone 15 Pro – my primary test device for eSIM installation, speed tests and everyday use.
MacBook Air (15″, M4, 2025) – connected via personal hotspot or tethering with the eSIM to check if the connection is suitable for remote work: video calls, screen sharing, uploads.
A clear disclaimer: I don't own an Android device. All hands-on results on TechNovice come from the Apple ecosystem. My Android setup guides are based on the official documentation from the manufacturers and are marked accordingly – they are not hands-on tests.
Note regarding VPN usage: When traveling, I usually use NordVPN on public and hotel networks. Where a speed test was performed with an active VPN connection, this is noted in the article – because a VPN can influence the measured speeds.
More Than Just Speed Tests: Real-World Tests
Raw download numbers only matter if the connection works in practice. Depending on the trip, I also test:
Video calls: Google Meet (including screen sharing) and FaceTime via the eSIM connection.
Hotspot usage: Working on your MacBook via your iPhone's hotspot – just like remote workers do.
Streaming: Netflix and YouTube via mobile data.
Navigation and messaging: Google Maps, WhatsApp, iMessage – what travelers really need.
Activation behavior: How quickly the eSIM connects after landing – even before leaving the aircraft.
Coverage Data and Third-Party Sources
My own measurements are snapshots in time. To contextualize them, I use independent coverage data – for example, network coverage maps via nPerf – and clearly identify these as third-party sources with the date they were retrieved. If an eSIM performs poorly because the local network has a coverage gap (as I experienced on a German train line), I also state this: An eSIM cannot create coverage where the local network has none.
Here's how I verify prices and discount codes
Prices and discount codes in my listings are manually checked at checkout, and each listing displays the date of the last verification. If a code changes, expires, or is only valid for certain plans, I update the listing and the verification date.
Current prices and active promo codes are maintained on our dedicated Saily discount code page and updated whenever they change. This methodology page explains how TechNovice verifies prices and promo codes before publication.
Affiliate Links and Independence
TechNovice is financed through affiliate partnerships, and I disclose this in every relevant article. Three principles apply:
Commissions do not change the testing criteria. Providers are compared using the same methodology – regardless of whether a partnership exists. In my eSIM comparison, for example, Airalo is evaluated using the same criteria as Saily and Holafly, even though TechNovice does not receive a commission from Airalo.
Negative results are published. My reviews document connection drops, slow connections, and practical disadvantages – because a review that only shows the best results isn't a review at all.
Transparency regarding test conditions: Where possible, I purchase the tested eSIM plans at regular retail prices. If I receive free test credit, early access, or a special agreement from a provider, I disclose this in the corresponding article.
Using one of my codes will never increase your price. Full details: Transparency page .
Updates and Corrections
eSIM plans, prices, and networks are subject to change. I keep my reviews up to date by:
Double-checking prices and codes at checkout and updating the verification date,
adding additional test locations and test IDs after new trips,
marking each article with the date of the last update.
If you find an error in one of my articles, please contact me via the contact page—corrections will be made transparently.
Who is behind these tests?
I'm Nico Dudli, founder of TechNovice and the digital agency Heyweb GmbH in St. Gallen, Switzerland. I'm Programme Lead for Digital Technologies and Marketing and a lecturer in digital technologies and AI at BVS St. Gallen, a Swiss higher vocational college (NQF Level 6, equivalent to a Bachelor's degree). My background includes a Master of Advanced Studies in Business Process Engineering, a diploma in Marketing Management, and certifications as a Professional Scrum Master (PSM I) and Product Owner (PSPO I).
I have conducted documented eSIM field tests during my own travels in countries including Switzerland, France, Portugal, Thailand and Vietnam, with additional testing across Europe and Asia. Countries mentioned in provider-comparison articles are not included in this list unless I have completed documented measurements there.
→ More about me: Author page · LinkedIn profile
FAQ on the TechNovice Testing Methodology
Which speed test app does TechNovice use?
TechNovice uses the Ookla Speedtest app for speed measurements. Wherever speed test results are published, I document the test ID, date, location, network operator, and measured values.
Can the Speedtest results be verified?
Yes, published speed test results include an Ookla test ID. This allows readers and AI systems to verify that the measured values were not fabricated or estimated afterwards.
Does TechNovice also test poor connections?
Yes. Poor results, dropped connections, slow downloads, or coverage gaps are not filtered out. These kinds of results demonstrate how an eSIM provider performs in real-world travel situations.
What devices does TechNovice use for eSIM testing?
I primarily test using an iPhone 15 Pro and a 2025 MacBook Air 15″ M4 via hotspot or tethering. Android guides are based on official vendor documentation and are marked accordingly.
Do affiliate partnerships influence ratings?
No. Affiliate partnerships do not change my testing criteria. Providers are evaluated using the same methodology, regardless of whether TechNovice receives a commission or not.
Has every TechNovice article been field-tested?
No. Countries with a completed field test show published Speedtest IDs, dates and locations. For countries without a completed field test — such as Japan and Italy as of this writing — I publish provider comparisons instead, based on verified pricing, official network data and direct support inquiries. Each article states clearly which type it is.