London Speed Test (Q4 2025): LHR vs City vs Tube Tunnels

29 Oct 2025

If you’re landing at Heathrow, dashing into the City, and spending hours on the Elizabeth line or deep Tube tunnels, here’s what London connectivity actually looks like in late 2025. We ran a multi-day london mobile speed test campaign across Heathrow (Terminals 2–5), the Square Mile and Canary Wharf, and key Underground corridors (Elizabeth line plus Jubilee, Victoria and Central), using dual 5G SA-capable devices on all major UK networks. We logged download/upload throughput, latency, jitter, dropouts and handover behaviour, and benchmarked against hotel Wi‑Fi in Zone 1 as a practical baseline for video calls and cloud work.

This report is traveller-first: expected speeds by place, what affects your connection, how 5G Standalone (SA) vs Non‑Standalone (NSA) behaves on the move, and simple steps to get reliable service underground. We’re publishing the full open CSV so you can slice by operator, line, station or hour of day—see the Data and reproducibility section for how to get it via our Partner Hub. If you’re planning a multi-country trip, pick the right eSIM up front via Destinations or region bundles like Esim Western Europe.

How we tested

Period: 7–11 October 2025 (Q4 snapshot)
Devices: iPhone 15 Pro and Pixel 8 Pro (both 5G SA/NSA capable)
Profiles: UK eSIM via Simology (multi-network testing), plus roaming checks on an EU plan (see Esim Western Europe)
Apps: Speedtest by Ookla, nPerf, and Fast.com for cross-validation
Samples: 1,524 tests; 40+ hours on trains and in stations; 12 hotel Wi‑Fi baselines (Zone 1)
Locations:
Heathrow T2/T3/T5 (landside and airside)
City of London (Bank, Moorgate, Liverpool Street), Canary Wharf
Elizabeth line (Paddington–Canary Wharf–Custom House), Jubilee, Victoria, Central
Metrics captured: median and p90 down/up Mbps, latency ms, jitter ms, packet loss %, disconnect events, 4G/5G SA/NSA state, handovers

How to replicate our approach (practical checklist): 1. Use a 5G SA-capable phone and ensure 5G SA is toggled on (where available). 2. Install two speed test apps to cross-check results. 3. Run 30–60 second tests stationary, and short bursts (10–15 seconds) in tunnels to reduce motion bias. 4. Log exact location and line/segment; note carriage position (front/middle/rear can matter near equipment rooms). 5. Capture background: time, crowding level, and whether Wi‑Fi or Wi‑Fi calling is on. 6. Repeat at different times (rush vs off-peak) to surface congestion.

Key findings at a glance

Heathrow (T2/T3/T5): Consistent 5G with high mid-band capacity; median download 180–280 Mbps airside, 120–200 Mbps landside; uplink 20–45 Mbps; latency typically 19–32 ms on SA.
City street level (Square Mile): Dense small-cell 5G delivers strong medians (220–350 Mbps) and low jitter; uplink 25–55 Mbps; lunchtime congestion is noticeable but rarely crippling.
Canary Wharf: Among the highest medians observed (260–400 Mbps) and very stable latency; great for quick syncs and uploads.
Elizabeth line: Best-in-class tunnels; median 150–250 Mbps with fewer dropouts and faster handovers; uplink 18–40 Mbps; latency 22–35 ms where SA is active.
Deep Tube (Jubilee/Victoria/Central): Coverage is now excellent across many tunnels, but performance is more variable than Elizabeth line; medians 60–140 Mbps; occasional 10–20 second dead zones in older sections and curves.
Hotel Wi‑Fi baseline (Zone 1 business hotels): Median 55–120 Mbps down, 15–35 Mbps up; latency 9–25 ms; predictable once you’re on Ethernet or a 5 GHz SSID; still beaten by good 5G for large uploads.

Heathrow (LHR): Terminals 2–5

What we measured - T5 airside (A gates): Median 240 Mbps down / 38 Mbps up; latency 21 ms; near-universal 5G with strong mid-band. - T3 arrivals hall: 150/28 Mbps median; occasional NSA fallbacks at peak arrivals create 10–15% higher latency. - T2 security area: 210/42 Mbps median; excellent for last-minute downloads; SA present for multiple operators. - Inter-terminal transit: Medians dip to 90–140 Mbps with brief handover stutters.

5G SA vs NSA - SA observed consistently in T2/T5; mixed SA/NSA in T3 landside. - SA improves uplink stability and cuts jitter by ~20–30% when crowds surge.

Traveller tips at Heathrow - Pro tip: After landing, toggle Airplane Mode off/on to force a clean attach; you’ll often jump from NSA to SA with a better uplink. - If your video upload stalls, move closer to windows or gate piers where small cells improve line-of-sight. - Avoid running multiple tests right at passport control—RF is noisy and crowded; results aren’t representative.

City core: Square Mile and Canary Wharf

Square Mile (Bank, Moorgate, Liverpool Street) - Street-level medians 220–320 Mbps; p90s often 500–650 Mbps with carrier aggregation. - Latency 18–28 ms on SA; 25–40 ms on NSA in busy pockets. - Building canyons can cause short fades; stepping 5–10 metres to a junction often restores full 5G.

Canary Wharf - Docklands is a standout: medians 260–400 Mbps; uplink 30–60 Mbps. - Lakeside promenades and concourses have excellent small-cell density; great for large OneDrive/Google Drive syncs.

Remote work practicality - 1080p Teams/Zoom is trivial on street-level 5G; 4K streaming is fine where medians exceed ~80 Mbps. - If your phone flips between SA and NSA during a call, expect a brief jitter spike; enabling Wi‑Fi calling on stable hotel or office Wi‑Fi can help.

Underground: Elizabeth line and deep tunnels

Elizabeth line (Paddington–Canary Wharf–Custom House) - Most reliable tunnel experience in our london mobile speed test: medians 150–250 Mbps, uplink 18–40 Mbps, latency 22–35 ms with SA prevalent. - Handover performance is notably smooth between stations; brief 1–3 second dips entering curves. - Platforms are even faster (200–350 Mbps) with strong beamforming and minimal congestion outside rush hour.

Jubilee, Victoria, Central (deep Tube) - Tunnels now widely covered but performance varies more than the Elizabeth line. - Jubilee: 100–180 Mbps medians, good uplink; occasional 5–8 second dropouts around tight curves. - Victoria: 80–140 Mbps; more NSA fallbacks at peak times cause higher jitter. - Central: 60–120 Mbps; some legacy sections show 10–20 second dead spots between stations.

How to keep calls stable underground - Use audio-only or 720p video in deep tunnels; save 1080p for the Elizabeth line or platforms. - Turn on Wi‑Fi calling; in many stations, the dedicated Wi‑Fi plus small-cell backhaul is steadier than constrained 5G uplink during crush loads. - If your device lets you, prefer 4G/5G “Auto” rather than “5G On” forced—forced 5G can cause sticky handovers underground.

Hotel Wi‑Fi baseline versus mobile

Zone 1 business hotels (12 properties) tested mid-evening:
Wi‑Fi medians 55–120 Mbps down, 15–35 Mbps up; latency 9–25 ms on 5 GHz; packet loss near zero once on Ethernet.
Peak-time streaming is predictable; large cloud backups (photos/videos) are often faster on 5G uplink if your room’s Wi‑Fi is congested.
Takeaway: For live calls and remote desktop, hotel Wi‑Fi (wired or strong 5 GHz) is safest. For bulk uploads, step outside on strong 5G if you need speed.

5G SA vs NSA: what travellers need to know

5G SA (Standalone) attaches directly to a 5G core. Benefits:
Lower latency (often 5–10 ms better than NSA).
More consistent uplink when networks are busy.
Cleaner handovers in modern tunnels (not universal yet).
5G NSA (Non‑Standalone) rides a 4G core. It’s widely available and still very fast, but jitter and latency are less predictable under load.
Roaming reality: Some roaming profiles still prefer NSA in parts of London even where SA exists. We saw SA for multiple operators in Heathrow and the City; NSA dominated on certain deep Tube segments during peaks.
Tip: If your plan supports VoLTE/VoNR, keep both enabled. Disable any “Low Data Mode” features while navigating or tethering laptops.

For multi-country travellers, a regional profile like Esim Western Europe reduces SIM swaps. If you’re arriving from the US and continuing on, compare with Esim North America or a country plan such as Esim United States. Heading to Paris, Rome or Barcelona next? See Esim France, Esim Italy and Esim Spain.

Data and reproducibility

Open data: We publish the raw measurements (Q4 2025 London Speed Tests) as an open CSV, with columns:
timestamp, device, operator, SA/NSA state, location (station/segment), GPS accuracy, down_mbps, up_mbps, latency_ms, jitter_ms, packet_loss_pct, dropout_flag
Access: Download the open CSV and documentation via our Partner Hub. Business users can request automated extracts and alerts through For Business.
Methods: Each location/segment includes at least 5 samples per operator. We discard outliers from failed attaches, plus first-second warm-ups in tunnels.
Attribution: Cite “Simology Connectivity Lab, London Q4 2025” with a link back to this report when using charts derived from the CSV.

Practical tips: make London connectivity work for you

Quick setup before you land - Install two test apps and download offline maps. - Add your eSIM profile in advance. For simple UK and Schengen coverage, use Esim Western Europe. - Enable VoLTE/VoNR and Wi‑Fi calling.

At Heathrow - After switching off Airplane Mode, wait 30–60 seconds for a 5G SA attach, then start navigation or ride-hailing. - If you need to upload large files, do it airside near gates where mid-band 5G is strongest.

On the Elizabeth line and Tube - Expect the Elizabeth line to handle 1080p video calls; switch to audio-first on older deep Tube tunnels. - Stand near carriage ends at stations if you must upload—platform small cells are often strongest there.

At the hotel - Prefer the 5 GHz SSID or Ethernet for calls; run one quick test to confirm stability. - Use your 5G uplink for big cloud backups if hotel Wi‑Fi drags below 10–15 Mbps up.

FAQ

What’s the fastest area from this london mobile speed test?
Canary Wharf led medians (260–400 Mbps), with the Elizabeth line platforms close behind. Heathrow T5 airside also performed very well.
Can I rely on mobile data in Tube tunnels now?
Largely yes. Elizabeth line is excellent end-to-end; Jubilee/Victoria/Central are broadly covered with the odd 10–20 second gap. Plan for brief dips and keep calls audio-first in older tunnels.
Does 5G SA work when roaming?
Often, but not everywhere. We saw SA on multiple operators in Heathrow and the City. Some roaming profiles still prefer NSA in parts of the network. It’s automatic—you can’t force SA if the profile or cell doesn’t allow it.
Is hotel Wi‑Fi better than 5G for video calls?
Usually, yes—if you’re on a clean 5 GHz SSID or Ethernet. Latency and jitter are steadier. For big file uploads, good 5G uplink can be faster than congested hotel Wi‑Fi.
What eSIM should I pick for a UK + Europe itinerary?
A regional option like Esim Western Europe keeps things simple across borders. If your trip includes North America legs, compare with Esim North America or specific country plans like Esim United States.
Where can I get the raw data?
The open CSV and methods guide are available on our Partner Hub. Teams needing regular updates should visit For Business.

Next step

Planning London plus onward travel? Choose a seamless plan for the UK and beyond via Destinations, then download the full dataset from our Partner Hub to plan your workdays with confidence.

Read more blogs

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Planning a south america itinerary 3 weeks through the high Andes? This route stitches together Peru’s Sacred Valley, Bolivia’s La Paz and Salar de Uyuni, Chile’s Atacama Desert, and northern Argentina’s quebradas or Mendoza wine country—often by long-distance bus and a couple of short flights. Connectivity is different at altitude: coverage is strong in cities but drops in high passes and salt flats; bus Wi‑Fi is patchy; border towns can be blackspots. The smart move is an eSIM with multi‑country coverage, backed by offline maps, offline translations, and a simple routine for crossing borders by bus without losing service. Below you’ll find a practical, connectivity-first itinerary; checklists to prep your phone, apps and documents; and on-the-ground tips for staying online where it matters: booking transport, hailing taxis, backing up photos, and navigating when the signal disappears.If you’re transiting via Europe or North America, you can also add a layover eSIM to stay connected door-to-door. Start with our country list on Destinations, then follow the steps, and you won’t waste time chasing SIM shops at 3,500 metres.The 3‑week Andes route at a glanceWeek 1: Peru (Cusco, Sacred Valley, Machu Picchu) - Fly into Cusco (or Lima then connect). - Base in Cusco; day trips to Pisac/Chinchero/Maras–Moray. - Train to Aguas Calientes; Machu Picchu visit; return to Cusco or continue to Puno/Lake Titicaca.Week 2: Bolivia and Chile (La Paz, Uyuni, San Pedro de Atacama) - Bus/collectivo via Copacabana to La Paz. - Fly or overnight bus to Uyuni. - 3‑day Uyuni–altiplano tour ending in San Pedro de Atacama (Chile).Week 3: Chile and Argentina (Atacama to Salta or Mendoza/Buenos Aires) - Choose: - North: San Pedro to Salta/Jujuy by bus; fly to Buenos Aires. - Or South: San Pedro–Calama flight to Santiago; bus or flight to Mendoza; onward to Buenos Aires.Connectivity notes (quick): - Cities: generally strong 4G/4G+; 5G in major hubs (Santiago, Buenos Aires). - Altitude/rural: expect long no‑signal stretches (Uyuni, altiplano passes, Paso Jama). - Bus Wi‑Fi: often advertised, rarely reliable. Plan to be offline onboard. - Border regions: networks switch; a multi‑country eSIM avoids sudden loss.eSIM vs local SIMs for a 4‑country tripFor a route with multiple borders and remote legs, eSIM wins on time and reliability.What a multi‑country eSIM gets you: - One plan across Peru, Bolivia, Chile, Argentina (check coverage per country on Destinations). - No passport/SIM registration queues at kiosks. - Keep your home number active on the physical SIM for calls/SMS codes. - Instant top‑ups if you burn data on photos or navigation.When a local SIM still helps: - Long stay in one country with heavy data use (e.g., a month in Buenos Aires). - Dead zones where a different local network performs better (rarely worth the hassle on a 3‑week pace).Practical approach: - Use an eSIM as your primary data line across all four countries. - If you find a specific local network far better in one region, add a cheap local SIM and keep the eSIM as backup.Device readiness checklist (before you fly)1) Check eSIM compatibility and SIM‑lock status on your phone.2) Buy and install your eSIM while on home Wi‑Fi. Keep a PDF/printed copy of the QR code.3) Label lines clearly (e.g., “eSIM Andes Data”, “Home SIM”).4) Turn on data roaming for the eSIM; leave roaming off for your home SIM to avoid charges.5) Set up dual‑SIM rules: data on eSIM; calls/SMS default to home SIM if needed.6) Download offline: Google Maps/Organic Maps for all target regions; language packs (Spanish at minimum); bus/air tickets; hotel confirmations.7) Cloud backups: set to upload on Wi‑Fi only; pre‑create shared albums for travel companions.8) Test tethering/hotspot with your laptop/tablet.If you’re transiting popular hubs, consider a short layover eSIM: - USA connections: add an Esim United States or a broader Esim North America.- Europe connections: Madrid/Barcelona? Use an Esim Spain. Paris or Rome? See Esim France and Esim Italy. Multi‑country layovers? Try Esim Western Europe.City‑by‑city connectivity notesCusco & the Sacred Valley (Peru)Coverage: Good in Cusco city; variable in high villages (Maras/Moray) and along Inca Trail approaches.Tips: Download Sacred Valley maps offline; pin viewpoints and ruins. most taxis use WhatsApp—save your accommodation’s number.Machu Picchu/Aguas Calientes: Patchy to none at the citadel. Upload your photos later; don’t rely on live ticket retrieval.Lake Titicaca: Puno and CopacabanaPuno: Reasonable 4G; bus terminals crowded—screenshot QR tickets.Crossing to Copacabana: Expect a signal drop around the border; have directions saved offline.La Paz (Bolivia)Good urban 4G; the cable car network has decent signal but tunnels do not.Yungas/“Death Road” tours: Mountain valleys cause dead zones—share your emergency contacts with the operator, carry a charged power bank, and don’t plan remote calls.Uyuni and the Altiplano (Bolivia to Chile)Uyuni town: OK 4G; ATMs finicky—use Wi‑Fi for banking apps.Salt flats/lagunas: Assume offline for most of the 3‑day tour. Guides often carry satellite phones; agree a pickup time/place in San Pedro and preload your map route.San Pedro de Atacama (Chile)Town: Solid 4G; accommodations often have Wi‑Fi but speeds vary.Geysers, Valle de la Luna: Offline navigation essential; sunrise trips start before mobile networks wake up in some areas.Salta/Jujuy or Mendoza/Buenos Aires (Argentina)Salta/Jujuy: Good city coverage; quebradas have long no‑signal sections.Mendoza: City 4G/5G; vineyards outside town can be patchy.Buenos Aires: Strong 4G/5G; ideal for cloud backups and large downloads before you fly home.Border crossings by bus: step‑by‑stepThe big ones on this route: Peru–Bolivia (Puno/Copacabana), Bolivia–Chile (Uyuni–San Pedro via Hito Cajón), Chile–Argentina (Paso Jama to Salta or Los Libertadores to Mendoza).How to keep service and sanity:1) The day before:- Top up your eSIM data.- Confirm your plan includes both countries you’re entering/leaving.- Download offline maps for both sides of the border and your town of arrival.- Save bus company WhatsApp and terminal address offline.2) On departure morning:- Keep a paper copy or offline PDF of tickets, insurance, and accommodation proof.- Charge phone and power bank; pack a short cable in your daypack.3) On the bus:- Don’t count on bus Wi‑Fi. Keep your eSIM as primary, but expect drops near mountain passes.- If your phone supports it, enable “Wi‑Fi calling” for later when you reach accommodation Wi‑Fi.4) At the border posts:- Data may be unavailable. Keep QR codes and booking numbers offline.- After exiting one country and entering the next, toggle Airplane Mode off/on to re‑register on the new network.- If the eSIM doesn’t attach, manually select a network in Mobile Settings.5) Arrival:- Send your accommodation a quick WhatsApp when you’re back online.- Recheck your eSIM’s data roaming is on; confirm you’re on an in‑country network, not a weak roaming partner.Pro tips: - Dual profiles: If your eSIM allows, keep a secondary profile for a different network in the same country—helpful in border towns.- Cash buffer: Some border terminals don’t accept cards; download a currency converter for offline use.Offline survival kit (5‑minute setup)Maps: Download regions for Cusco, Sacred Valley, Puno, La Paz, Uyuni, San Pedro, Salta/Jujuy or Mendoza, and Buenos Aires.Translations: Download Spanish for offline use; add phrasebook favourites (bus tickets, directions, dietary needs).Documents: Save PDFs of passports, tickets, hotel addresses; star them for quick access.Rides: Screenshots of pickup points; pin bus terminals and hotel doors.Entertainment: Podcasts and playlists for long bus legs, set to download on Wi‑Fi only.Altitude and your tech: what changesCoverage gaps lengthen: Fewer towers at high altitude; valleys can block signal. Assume offline on remote excursions.Batteries drain faster in cold: Keep your phone warm and carry a power bank (10,000–20,000 mAh).Hotel Wi‑Fi may be congested: Schedule big uploads (photo backups, app updates) for big-city stays like Santiago or Buenos Aires.GPS still works offline: Your blue dot shows on offline maps without data—preload everything.Data budgeting for 3 weeksTypical traveller usage across this route: - Messaging/Maps/Bookings: 0.2–0.5 GB/day- Social and photo sharing: 0.3–0.7 GB/day- Occasional video calls/streaming: 0.5–1.0 GB/dayFor a mixed-use trip, plan 15–25 GB for 3 weeks. Heavy creators should double it and upload over hotel Wi‑Fi when possible. If you work remotely, consider a higher‑capacity plan and a backup eSIM; see our guidance on For Business.Practical route with transport and connectivity cuesDays 1–4 Cusco base: Strong city signal; day trips may be spotty—go offline-ready.Days 5–6 Machu Picchu: Expect no service at the ruins; sync tickets ahead.Days 7–8 Puno to La Paz via Copacabana: Border signal drop; re‑register networks after crossing.Days 9–11 Uyuni tour to San Pedro: Treat as offline; charge nightly; carry spare cables.Days 12–14 San Pedro: Stable in town; tours offline; top up data before Paso Jama.Days 15–17 Salta/Jujuy or Mendoza: Good urban 4G; rural patches are offline.Days 18–21 Buenos Aires: Strongest connectivity of the trip; clear your uploads and map downloads for the flight home.Partnering and stopover extrasHospitality and tour operators in the Andes: help your guests stay connected—explore co‑branded solutions via our Partner Hub.Transatlantic flyers: test your eSIM setup on a layover with an Esim United States or Esim Western Europe before hitting high-altitude blackspots.FAQs1) Do I need a local SIM in each country?No. A multi‑country eSIM covering Peru, Bolivia, Chile and Argentina is simpler and works well for a 3‑week pace. Consider a local SIM only if you’ll spend longer in one country and want the absolute best regional coverage.2) Will my WhatsApp number change with an eSIM?No. WhatsApp is tied to your registered number, not your data line. Keep your home SIM active for voice/SMS (roaming off if you wish), and use the eSIM for data—WhatsApp continues as normal.3) Can I hotspot to my laptop or camera?Yes. Enable tethering on your eSIM. Mind your data: cloud backups and OS updates can burn gigabytes—set them to Wi‑Fi only or schedule in big cities.4) What if there’s no signal on the Uyuni/Atacama legs?That’s expected. GPS still works offline. Pre-download maps and translations, carry a power bank, and sync plans with your tour operator before departure.5) Will I get roaming charges at borders?If you’re using a multi‑country eSIM with coverage in both countries, you won’t incur extra roaming fees from your home carrier. Keep roaming off on your home SIM to avoid accidental use.6) I’m connecting via Europe or the US—worth getting a layover eSIM?Yes. It’s an easy way to test your setup and stay reachable. Try Esim North America or country options like Esim Spain, Esim France, or Esim Italy for common hubs.Next step: Browse South America coverage options and build your plan on Destinations.

31 Oct 2025

5G SA vs 5G NSA vs 4G LTE: Real‑World Differences for Travellers

If you travel with a 5G phone, you’ve probably seen network icons flip between LTE, 5G and sometimes 5G+. But what actually changes for you on the road? In short: 4G LTE is the baseline, 5G NSA (Non‑Standalone) rides on a 4G core, and 5G SA (Standalone) runs on a pure 5G core. That core difference affects latency, upload throughput, stability in crowded places, and even battery life. This guide breaks down 5g sa vs nsa in plain English, with a focus on what you’ll notice when tethering, video calling, using maps in busy city centres, and moving across borders. We also share what our Speed Tests suggest across popular destinations, and how to set up your phone for the best result. Expect plenty of 5G NSA while roaming today; 5G SA is growing but still patchy. If you need predictable performance, we’ll show you when to embrace SA—and when to simply lock to 4G LTE to save battery and frustration.Quick definitions (and why they matter)4G LTEThe workhorse network most travellers still rely on. Mature coverage, solid stability, decent downloads, and predictable voice via VoLTE.5G NSA (Non‑Standalone)Uses 5G radio for data but anchors control (and often uplink) on a 4G core. It’s the most common “5G” you’ll see, especially when roaming.5G SA (Standalone)Uses a 5G core end‑to‑end. That unlocks consistently lower latency, faster uploads on the same cell, and new features (e.g., slicing) as networks enable them.Why it matters: - Latency: SA removes 4G core bottlenecks, cutting response times—handy for maps, calls and cloud tools. - Uploads: SA can enable true 5G uplink, boosting video calls and backup speeds. - Battery: NSA can use dual connectivity (4G + 5G), which can drain faster in fringe coverage. SA is often more efficient—when coverage is strong. - Roaming: SA roaming is still limited. Most travel eSIMs attach to NSA or 4G LTE.5g sa vs nsa: what you’ll notice on the roadLatency and responsivenessNSA typically delivers ping times similar to 4G once you factor in the 4G core, often 30–60 ms in good conditions.SA removes the 4G core and can shave meaningful milliseconds—think high‑20s to mid‑30s ms in many cities, assuming decent backhaul.Real‑world impact: maps load a bit snappier, web pages feel more instant, cloud apps and collaboration tools respond quicker, and gaming feels less “sticky.” The difference is most visible under load (busy cells) or when you’re tethering a laptop.Uploads: video calls and cloud backupOn NSA, the uplink often still rides 4G, which can cap real‑world upload speeds even when your download looks great.On SA, networks can enable 5G uplink on the same spectrum, delivering noticeably higher upload throughput and lower jitter.Real‑world impact: clearer video calls, quicker photo/video backups, and smoother live streaming from events or viewpoints.Coverage and stabilityNSA tends to be more available because operators can bolt 5G radios onto existing 4G cores. That’s why it’s what you see most when roaming.SA coverage is growing but more concentrated in major urban areas and busy venues. When you do get it, performance is often steadier at peak times.Expect more network “mode flipping” on NSA at cell edges (5G→4G), which can interrupt downloads or calls mid‑handover.Battery life differencesNSA’s dual connectivity can increase radio activity, especially if your phone hops between 5G and 4G frequently.SA can be more power‑efficient because it doesn’t maintain a 4G anchor, but this benefit shows mainly when you have solid SA coverage and a recent modem.Practical tip: if you’re in a fringe 5G area and watching your battery, forcing LTE can extend life without a big hit to usability.Hotspot and tetheringSA’s lower latency and stronger uplink help when tethering multiple devices—uploads, real‑time collaboration, and video calls hold up better.NSA is still fine for general browsing and streaming, but group calls can get choppy when the uplink saturates.Where 5G SA actually helps travellers todayCongested hubs: large stations, stadium districts, city centres at rush hour. SA cores manage traffic more efficiently; uploads and responsiveness hold up better.Video‑forward tasks: live streaming, HD video calls, and rapid photo backups to the cloud benefit from SA’s uplink and lower jitter.Work on the move: if you rely on real‑time tools (Slack/Teams, SSH/RDP, cloud IDEs), SA’s latency advantage is noticeable.Modern devices: newer 5G chipsets (and carrier bundles) squeeze more consistency and efficiency from SA.Pro tip: - If your phone shows 5G but uploads are stuck under 10 Mbps and calls feel laggy, you’re likely on NSA with 4G uplink. Move a block or two, or toggle aeroplane mode; if SA is available, your device may attach to it on reconnection.Country notes and what to expectUnited StatesMajor urban areas increasingly run SA on at least one network. Roamers, however, often land on NSA or 4G depending on agreements and device support. Our advice: expect NSA, enjoy SA where available, and don’t rely on mmWave. Planning a trip? See our country profile: Esim United States.Western EuropeSA rollouts are underway in many capitals and transport corridors, but NSA remains the default roaming experience for now. Expect consistent NSA with bursts of SA in city centres. Explore regional options on Esim Western Europe, and country specifics: Esim France, Esim Spain, and Esim Italy.Cross‑border North AmericaIf you’re moving between the US, Canada and Mexico, pick a plan designed for multi‑country roaming—coverage consistency matters more than chasing SA. Start with Esim North America.City‑by‑city expectationsSA tends to appear first in dense urban cores, new business districts and large venues. Rural and suburban areas often stick with NSA/4G longer. For current notes and crowd‑sourced Speed Tests, browse your target country and city pages via Destinations.For teams and frequent flyers: - If connectivity is mission‑critical, we can help you choose profiles and carriers with the best SA footprint for your itinerary. Learn more For Business or connect via our Partner Hub.How to check and optimise your setupFollow this quick checklist before you fly and when you land.1) Confirm device and OS support- Check that your handset supports your destination’s 5G bands and SA capability. Most flagship phones from 2021 onwards do; mid‑range varies.- Update OS and carrier settings. SA often requires recent carrier bundles.2) Add your eSIM and enable data roaming- Install your Simology eSIM before you depart where possible.- On arrival, toggle data roaming on and wait a minute. If you see 5G right away, great; if not, give it a few minutes and try aeroplane mode on/off.3) Choose the right network mode- iPhone: Settings → Mobile Data → Voice & Data → 5G Auto is a good balance; use 5G On if you specifically want to test SA.- Android (varies): Settings → Network & Internet → SIMs → Preferred network type → Select 5G where available.4) Verify what you’re on- Run a quick speed/latency test in two spots (indoors and outdoors). Note the ping and upload.- If latency is high and upload is weak despite “5G”, you’re likely on NSA; move to a more open area or closer to the city core to try for SA.5) Optimise for your task- Video calls/live streaming: prioritise signal quality (near windows, outdoors). If SA isn’t available, consider 4G LTE if 5G NSA is unstable.- Battery conservation day: lock to LTE, reduce background sync, and use low‑data mode where possible.6) Fix flaky behaviour fast- Toggle aeroplane mode or briefly disable/enable 5G.- If roaming, try the next preferred network in your SIM settings (some profiles allow manual carrier selection).- Reboot if handovers get “stuck” between 5G and 4G.Pro tips: - Don’t chase 5G at all costs. A strong 4G LTE signal can beat a weak NSA signal for practical tasks.- For hotspotting a team, position the phone high and near a window; uplink improves and SA is more likely to attach in stronger signal zones.Real‑world Speed Tests: what we seeFrom our ongoing Speed Tests in major cities, three patterns stand out: - Uploads are the biggest win for SA. In the same cell, SA often delivers 1.5–3× higher uplink than NSA, with less jitter—transformative for HD calls and backups. - Latency is reliably lower on SA, but the size of the improvement depends on the operator’s backhaul and peering. Expect a meaningful reduction rather than miracles. - Downloads vary with spectrum more than SA/NSA status. Wide mid‑band (e.g., 100 MHz) shines on both NSA and SA; SA simply makes it more consistent in crowds.Want to compare by country and city? Browse our live notes via Destinations.FAQIs 5G SA worth it for travellers?Yes—when available. You’ll feel it most in latency‑sensitive and upload‑heavy tasks (video calls, cloud collaboration). But because SA roaming is still limited, plan for strong NSA or LTE as your baseline.Will my travel eSIM get 5G SA or only NSA?It depends on local partners, your device, and carrier agreements. Many roamers attach to NSA today. SA is expanding in big cities; check your destination on Destinations for current notes.Why are my uploads slow even though it says 5G?You’re likely on NSA with a 4G uplink. Move to a stronger signal area, toggle aeroplane mode to re‑attach, or try again in a busier urban zone where SA may be present.Does 5G drain my battery faster than 4G?It can—especially NSA at the edges of coverage. SA can be more efficient in strong coverage. If battery is critical, lock to LTE and re‑enable 5G when you need peak performance.Will 5G work on my older phone?Many 2020–2021 handsets handle NSA well but may lack full SA support on all bands or carriers. Keep your OS and carrier settings updated to unlock the widest compatibility.Do I need special settings for voice on 5G SA?Voice usually runs over VoLTE today; some networks enable VoNR on SA. Ensure VoLTE is on and your carrier settings are current. If calls fail on SA, your phone will typically fall back gracefully.Bottom lineNSA is the 5G you’ll meet most while roaming; it’s faster than 4G for downloads but often feels “4G‑ish” for uploads and latency.SA is the real step forward for responsiveness and uplink—great for work, calls and backups—yet currently concentrated in major hubs.Optimise pragmatically: use SA when it’s strong; prefer LTE over weak NSA to save battery and frustration.Next step: pick your destination and see current network notes and Speed Tests on Destinations. If you’re planning a multi‑country trip, start with Esim Western Europe or Esim North America. For teams, talk to us For Business or via our Partner Hub.

29 Oct 2025

Case Study Template: How a Travel Brand Launched in 6 Weeks (KPIs & Lessons)

Looking to add eSIM to your travel product without becoming a telco? This reusable case study template distils how a mid-sized travel brand launched a white-label eSIM shop in just six weeks, what they measured, and how they iterated. You’ll get a practical timeline, checklists, KPIs (activation rate, CAC, ARPU and more), pitfalls to avoid, and the wins worth replicating. Use it to scope your own white-label rollout with confidence and keep your team focused on what travellers actually need: fast purchase, easy install, and reliable coverage in the places they go. The example below references common launch destinations such as the United States, France, Spain and Italy, plus regional bundles for Western Europe and North America, so you can map to your own catalogue from day one. If you’re evaluating partners, you can compare what’s realistic against this blueprint and adapt the numbers to your brand’s audience size and channels.Who this eSIM case study template is forTravel brands, OTAs and airlines exploring “esim case study white label” optionsFintechs, super-apps and loyalty programmes adding a simple, high-margin travel utilityWholesale/partnership teams validating timelines, KPIs and GTM costsIf you need a quick view of coverage and plans by country, skim the live catalogue at Destinations, including Esim United States, Esim France, Esim Spain, Esim Italy, Esim Western Europe and Esim North America.The 6‑week launch timeline (reusable)This is a realistic, low-lift plan for a white-label eSIM powered by an established provider.Week 1: Discovery and commercial basicsDefine goals: attach rate target, first-90-day GMV, acceptable CAC, initial ARPU target.Choose launch catalogue: 4–6 high-volume routes (e.g., US, France, Spain, Italy) plus 1–2 regional bundles (Western Europe, North America).Confirm commercial model: wholesale pricing, revenue share/margin, payment flows, refund rules.Legal/brand: co-branding, domain/subdomain, T&Cs alignment.Pro tip: Start with 20–30 SKUs max. More choice rarely improves conversion at launch.Week 2: Integration planningSelect integration path: hosted white-label storefront vs. embedded SDK/API.Map flows: purchase, email delivery, in-app QR, on-device install, top-ups, refunds.Analytics plan: events for view → add to cart → purchase → install → activation → top-up.Support model: Tier 1 handled by you with provider escalation for network issues.Checklist - Tracking IDs/UTMs set - Payment processor connected - Support macros drafted - Landing pages and FAQs draftedWeek 3: Build and contentConfigure storefront: brand, colours, copy, pricing rules, currency.Localise essential pages and install guides (EN + top languages in your audience).Add plan cards for Esim United States, Esim France, Esim Spain, Esim Italy.Create regional bundles for Esim Western Europe and Esim North America.Pro tip: Add “Install before you fly” guidance in the checkout and confirmation email to boost activation rate.Week 4: QA and pilotDevice testing: iPhone and Android across 8–10 common models.Pilot cohort: 50–200 real users from your newsletter or loyalty members.Validate KPIs: funnel steps, install success, activation within 24 hours, support ticket rate.Week 5: Go-live and paid mediaLaunch channels: email, app push, post-booking pages, and route-specific pages.Paid tests: small budgets on search and social (brand + destination keywords).Partnerships: cross-sell with travel insurance and airport transfer pages.Pro tip: Put eSIM into your post-booking confirmation flow; travellers are primed to buy connectivity right after itinerary confirmation.Week 6: Optimise and scaleIterate on pricing tiers and bundles.Add top-ups and auto-refill.Roll out additional countries from Destinations.Localise support macros based on real ticket themes.The KPI framework that actually mattersTrack these weekly, then lock a monthly view for management.Activation Rate: percentage of purchased eSIMs that successfully activate within 7 days. Target >90% with clear install guides and pre-travel prompts.CAC (Customer Acquisition Cost): paid media + creative + attributable fees divided by first purchases. Keep under 25–35% of first-order revenue at launch.ARPU (Average Revenue per User): total eSIM revenue / unique purchasers over 30–90 days. Track first-order ARPU and 60-day ARPU including top-ups.Refund Rate: proportion of orders refunded. Target <4%. High refund rates often signal install confusion, not network issues.Attach Rate: percentage of core bookings that include an eSIM add-on. Good early target: 3–7% on relevant routes.NPS / CSAT: collect post-activation; aim for 60+ with simple install and clear coverage notes.Support Ticket Rate: tickets per 100 orders. Target <10/100 after week 2.Optional, but useful: - Top-up Ratio: customers who purchase additional data within 30 days (indicator of retention). - Gross Margin: after wholesale rate, payment fees and refunds. - CLV: early proxy is first order + 60-day top-ups; refine later.Pro tip: Separate install failure from “no service” tickets in your dashboard. The fix for each is different.Example baseline metrics from similar launchesUse these as a starting point; adjust to your brand and channel mix.Activation Rate: 92–96% within 7 daysCAC: £3–£7 (email/owned), £8–£15 (paid search), £10–£18 (paid social)First-order ARPU: £10–£18 (country), £18–£28 (regional bundle)Refund Rate: 1.5–3.5%Ticket Rate: 6–12 per 100 orders (drops below 6 with better guides)Attach Rate (post-booking page): 4–8%Reusable case study outline (fill-in template)Use this structure to document your launch for stakeholders or for partner due diligence.Context - Brand: industry, monthly travellers, top routes - Objectives: revenue, attach rate, NPS, time-to-market - Constraints: dev capacity, support hours, languagesSolution - White-label approach: hosted storefront vs. embedded - Catalogue at launch: list SKUs (e.g., US, France, Spain, Italy, Western Europe, North America) - Pricing strategy: country vs. regional bundle, 7/15/30-day tiers - Support model: Tier 1 scripts, escalation pathImplementation - Timeline: 6 weeks with key milestones - Integrations: payments, analytics, CRM, attribution - Content: install guides, FAQs, post-purchase emails - QA: device matrix, test results, pilot cohortResults (first 60–90 days) - KPIs: Activation, CAC, ARPU, refunds, ticket rate - Revenue and margin: by SKU and channel - Learnings: what moved conversion, what reduced ticketsNext steps - Catalogue expansion from Destinations - Automation: top-up prompts, auto-refill - Localisation and partner bundlesPro tip: Keep the outline in a shared doc and update weekly for the first month; it becomes your internal “runbook”.Pricing, packaging and catalogue strategyKeep it simple: three durations (7, 15, 30 days) and two data tiers per country.Bundle where it helps: Esim Western Europe and Esim North America convert well for multi-city trips.Anchor value with examples: “2GB is enough for maps + messaging on a weekend in Paris; consider 5GB for longer stays.”Promote hero SKUs early: Esim United States, Esim France, Esim Spain, Esim Italy.Pro tip: Nudge buyers to top up in-app before roaming data runs out; it reduces support and increases ARPU.UX and content that drives activationPre-travel prompt: “Install before you fly” banner + email reminder 24 hours pre-departure.One-screen install: clear QR code, device-specific steps, and a 60-second video link.Plain-English coverage notes: where 5G/4G is available; hotspot policy.Troubleshooting microcopy: “Toggle Airplane Mode, ensure eSIM is set to ‘Data’ line, turn on Data Roaming.”Post-purchase checklist:Add eSIMSet as data lineKeep primary SIM for callsEnable data roamingRestart on arrivalPro tip: Show estimated daily usage examples (Maps, WhatsApp, ride-hailing). It reduces “ran out too fast” tickets.Support playbook (Tier 1)Install issues (most common)Ask device model and OSConfirm eSIM is set as the data lineToggle data roaming and restartIf still failing, escalate with order ID and ICCIDNo data on arrivalCheck APN settings (auto vs. manual)Confirm local network availabilityToggle airplane mode, select network manuallyUnexpected consumptionCheck OS updates and background syncSuggest low data mode and turning off iCloud Photos/Drive on mobile dataTarget response under 5 minutes on live chat during business hours; under 2 hours via email.Common pitfalls and how to avoid themToo many SKUs on day oneStart with 6–8. Expand when you see real demand.Vague install instructionsUse device-specific steps and screenshots. Link them in the checkout and email.No pre-travel remindersActivation rate can drop 10+ points without them.Misaligned pricing to local competitionCheck live pricing frequently; adjust small deltas rather than big swings.Under-investing in analyticsTrack install and activation, not just purchases. It’s where experience breaks.Pro tip: Treat refunds as a learning loop; tag each with a concise reason and fix the top two drivers weekly.What made this launch work (wins to replicate)Traveller-first copy and support reduced tickets by 41% after week 2.Regional bundles lifted ARPU by 22% without hurting conversion.Post-booking placement drove a 6.2% attach rate versus 2.1% on generic pages.Pre-departure reminders improved activation from 88% to 95%.A small, curated catalogue made the decision easy and boosted checkout completion by 9%.What to ask a white-label eSIM partnerCatalogue breadth and depth: Are priority markets covered with 4G/5G? See live Destinations.Commercials: Clear wholesale rates, currency, settlement, and refund policies.Integration options: Hosted storefront, SDK or API? Time to live?Analytics: Event-level data for install and activation.Support: SLAs, escalation, and proactive network incident notices.Compliance and security: Data handling, PCI scope for payments, uptime.For enterprise requirements and wholesale pricing, explore For Business and the partner resources in the Partner Hub.Quick launch checklistObjectives set (attach, ARPU, activation)6–8 SKUs selected (US, FR, ES, IT + 1–2 regional bundles)White-label storefront themed and pricedInstall guides and FAQs publishedAnalytics and attribution wiredPilot cohort completed and fixes appliedGo-live across post-booking, email, and appWeekly KPI review and content optimisationFAQ1) What does “white-label eSIM” mean?A ready-made eSIM storefront or component you brand as your own. The provider handles the telecom backend; you focus on UX, marketing and support.2) How fast can we realistically launch?With a hosted white label, six weeks is achievable, including QA and a pilot. Embedded SDK/API integrations may add 1–3 weeks depending on your app release cycle.3) Which destinations should we start with?Prioritise top routes and high-volume tourist markets: Esim United States, Esim France, Esim Spain, Esim Italy, plus bundles like Esim Western Europe and Esim North America.4) How do we keep activation rates high?Send pre-departure reminders, offer clear device-specific install steps, and make sure data roaming is on for the eSIM line. Keep troubleshooting one tap away in the order email.5) What margins are typical?It depends on wholesale rates and pricing, but many brands target 25–45% gross margin after payment fees and refunds, with regional bundles often carrying higher ARPU.6) Do we need 24/7 support from day one?Not necessarily. Start with expanded hours around peak departure times and clear self-serve guidance. Add 24/7 coverage once volumes justify it.Next step: Ready to scope your own white‑label rollout and see commercial options? Visit the Simology Partner Hub.

29 Oct 2025