Sydney Speed Test: SYD Airport, CBD, Bondi – 5G Expectations vs Reality

31 Oct 2025

Sydney is one of the easiest places in Australia to get online fast—if you know where to stand and what your phone is actually connecting to. We spent two days running a structured sydney mobile speed test across three real traveller zones: Sydney Airport (SYD, T1/T2/T3), the CBD (Circular Quay to Town Hall via Martin Place), and Bondi (promenade, Icebergs and backstreets). We measured download, upload and latency on Australia’s big three networks with modern flagship phones, recording whether 5G was Standalone (SA) or Non‑Standalone (NSA), plus band behaviour where visible. The headline: Sydney 5G can be blistering in CBD mmWave pockets, solid but variable at Bondi, and good-enough at SYD—yet uplink and consistency still hinge on NSA 4G anchors in many spots. Below you’ll find results, practical traveller tips, and an open CSV preview you can reproduce. For more field tests in other cities, check our Destinations.

What we tested and how

Locations and times

SYD Airport
T1 International arrivals hall and kerbside
T2/T3 landside check-in zones
Airport rail platforms
Time windows: 07:30–09:30 and 17:00–19:00 (peak passenger flow)
Sydney CBD
Circular Quay ferry concourse
George St (Town Hall to Wynyard), Martin Place, Pitt St Mall
Known mmWave trial/coverage pockets near Martin Place/George St
Time windows: 10:00–12:00 and 13:00–15:00 (lunch-time load)
Bondi
Promenade (central), Bondi Icebergs, Hall St/Campbell Pde backstreets
On the sand (middle of the beach) vs against the seawall
Time windows: 08:00–10:00 (quiet) and 16:30–18:30 (busy sunset)

Devices, SIMs and apps

Handsets: recent flagships supporting 5G n78 mid‑band and n258 mmWave (where available). Mixed iOS and Android to observe stack differences.
SIMs: local prepaid eSIMs from each national operator to avoid roaming variability. Dual‑SIM kept idle on secondary line.
Measurement: Ookla Speedtest, nPerf and Fast.com, with 3–5 runs per spot; best‑of‑median recorded. Location logged at street precision.
Network notes: we recorded SA vs NSA where the device exposed it and noted apparent bands (e.g., n78, n258). Many phones still default to NSA in Sydney even where SA is selectively live.

Results at a glance

SYD Airport (landsid e)
Typical 5G NSA downlink: 120–300 Mbps; uplink: 10–30 Mbps; latency: 18–28 ms.
Peak pockets near T1 kerbside reached ~420 Mbps down. Platforms were more variable due to structure and passenger density.
Sydney CBD
Mid‑band 5G NSA median: 300–500 Mbps down; uplink: 20–60 Mbps; latency: 12–22 ms.
mmWave pockets (where reachable line‑of‑sight): 800–1,400+ Mbps down; uplink: 70–120 Mbps; latency often sub‑12 ms. Coverage is highly directional and sensitive to body blocking.
Bondi
Promenade (mid‑band): 180–350 Mbps down late morning; often drops to 80–200 Mbps at sunset load.
On the sand: speeds typically halve compared to the seawall due to distance, downtilt and body/sea reflections; uplink can dip <10 Mbps on NSA.
Backstreets (Hall St/Campbell Pde): often outperform the beach itself (250–400 Mbps) thanks to closer small cells and better geometry.

5G SA vs NSA: SA sessions were sporadically observed in the CBD (low‑band or mid‑band), delivering steadier latency but not always higher throughput. Most high headline speeds still came from NSA with a strong 4G anchor plus wide 5G n78.

Detailed findings

SYD Airport: solid, sometimes spiky

Arrivals halls favour coverage over capacity. Expect 5G NSA in most open areas, with frequent handovers around glass and metal structures.
Best results were kerbside at T1 where devices saw cleaner sectors: ~350–420 Mbps down, 20–35 Mbps up.
Platforms showed the widest variance due to tunnel geometry; we saw 60–250 Mbps down with occasional 4G fall‑backs providing steadier uploads (~15–25 Mbps).
SA appeared briefly on one handset on low‑band, with latency improvement (to ~14 ms) but no throughput gain vs solid NSA.

Traveller tip: if your upload matters (video, large files), step outside towards open sky or near terminal windows for a better uplink path.

CBD: mmWave moments, mid‑band muscle

Mid‑band n78 carried most sessions, returning consistent 300–500 Mbps down and 25–60 Mbps up at lunchtime.
We hit mmWave near Martin Place/George St with line‑of‑sight: 1.1–1.4 Gbps down, 80–120 Mbps up. Move a few metres, turn a corner, or stand behind a bus shelter and mmWave vanishes.
SA showed on a subset of devices. It improved jitter and call setup times but didn’t beat top NSA downlink where wide 5G + robust 4G anchor was present.

Traveller tip: to catch mmWave, stand streetside with a clear view of small‑cell nodes, keep the phone unobstructed, and face the likely sector. If speeds seem oddly low, turn 90 degrees—your body can block mmWave.

Bondi: beachfront variance, timing matters

Along the seawall, mid‑band 5G posted 180–350 Mbps down late morning with 15–35 Mbps up. At sunset, crowding pushed many sessions to 90–180 Mbps down and single‑digit uploads on NSA.
On the sand, even 30–50 metres from the seawall cost ~30–60% throughput due to antenna downtilt and body/hand absorption, especially if seated.
Icebergs lookout performed well (clean elevation): 280–420 Mbps down; backstreets off Hall St often matched or beat the promenade, suggesting small‑cell offload.
SA sightings were rare at the beach during our windows. NSA dominated, and uplink limits were noticeable for live streaming.

Traveller tip: for a clear video call at sunset, step off the sand to Campbell Parade or a café window seat. You’ll likely gain a stronger uplink.

5G SA vs NSA in Sydney: what it means for you

NSA (Non‑Standalone): your 5G piggybacks on a 4G core anchor. Often delivers higher peak speeds today because 4G+5G work together with mature scheduling. Uplink may be constrained by the 4G anchor path.
SA (Standalone): true 5G core. Potentially better latency, uplink and reliability for calls and enterprise features (network slicing later). Coverage is still being optimised; some consumer devices don’t hold SA consistently.
What we observed: CBD had the best chance of SA on compatible devices; airport and Bondi leaned NSA. Peak downlink wins still came from broad NSA deployments; SA helped with jitter and call stability.

How to check: - iPhone: Settings > Mobile Data > SIM > Voice & Data shows 5G status; deeper field metrics vary by model. - Android: Settings > About Phone > SIM Status, or vendor service menus. Look for “NR SA/NSA.”

Traveller setup checklist for better Sydney speeds

Update your device OS and carrier settings before you land.
Use a local eSIM for the three networks if you need redundancy. For multi‑city trips, see Destinations.
Turn off Low Data/Data Saver while testing; disable VPN for raw measurements.
Test outdoors first; then move inside near windows. Re‑run at shoulder height, phone vertical.
For uploads, prefer locations with line‑of‑sight to the street and fewer bodies between you and the cell.
If speeds jump wildly, toggle airplane mode or 5G off/on to refresh the anchor.
Need guaranteed performance for a team? Our For Business team can pre‑provision multiple eSIM profiles and fallback plans.

Pro tips: - mmWave: treat it like light—needs a clean path. A backpack, your hand, or a bus can kill it. - Bondi: early morning beats sunset for both capacity and uplink. - Airport: step outside for uplink; inside favours coverage and stability over raw speed.

Reproduce our test (step‑by‑step)

Activate a local prepaid eSIM on a recent 5G phone. Keep any secondary line idle.
Disable Wi‑Fi and VPN. Confirm 5G is enabled and not in “Auto 4G preferred.”
Install two test apps (e.g., Speedtest and nPerf). Select the same target server where possible.
At each spot, run 3–5 tests per app, 30–60 seconds apart. Log the median result.
Note SA/NSA state if exposed; record time, GPS, and any obvious obstructions (bus shelter, tree, crowds).
Repeat at different times of day to see load effects.
Export to CSV. Compare with our open dataset via the Partner Hub.

Dataset and method (open CSV)

Columns - timestamp (local), location, operator, tech (5G SA/NSA or 4G), anchor (if NSA), down_mbps, up_mbps, latency_ms, notes

CSV preview (10 rows) timestamp,location,operator,tech,anchor,down_mbps,up_mbps,latency_ms,notes
2025-03-12 08:14,SYD T1 kerbside,Operator A,5G NSA,4G+NR n78,418,32,19,Clear LOS to mast
2025-03-12 08:42,SYD T1 arrivals hall,Operator B,5G NSA,4G+NR n78,236,21,23,Busy footfall
2025-03-12 09:08,Airport Rail Platform,Operator C,4G LTE,,92,18,31,Partial 5G fallback
2025-03-12 11:26,Martin Place (LOS),Operator A,5G mmWave NSA,4G+NR n258,1382,106,9,Line-of-sight small cell
2025-03-12 12:04,Pitt St Mall,Operator B,5G NSA,4G+NR n78,354,41,17,Lunch crowd
2025-03-12 13:32,Circular Quay concourse,Operator C,5G NSA,4G+NR n78,287,27,20,Open sky
2025-03-12 08:58,Bondi Promenade (centre),Operator A,5G NSA,4G+NR n78,312,24,18,Morning light load
2025-03-12 17:22,Bondi on the sand,Operator B,5G NSA,4G+NR n78,128,8,24,Sunset crowd; body blocking
2025-03-12 17:56,Icebergs lookout,Operator C,5G NSA,4G+NR n78,402,36,16,Elevated position
2025-03-12 18:18,Hall St backstreet,Operator B,5G SA,,368,52,14,Steady SA session

Full, open CSV and collection notes are available via the Partner Hub. You are free to use and cite with attribution.

Who should care about this

Solo travellers and remote workers needing reliable uplink for calls and cloud saves.
Teams running live content at Bondi or events in the CBD. Our For Business solutions include pre‑trip planning, eSIM pools and on‑site fallback.
Travellers continuing onward: if Sydney is a stopover before North America or Europe, line up your cross‑region eSIMs now:
For the US leg: see Esim United States or broader Esim North America.
For Europe legs: check Esim Western Europe, plus country options like Esim France, Esim Italy and Esim Spain.

FAQs

Is 5G SA widely available in Sydney?
Selective. We observed SA sessions mainly in the CBD on compatible devices. Most day‑to‑day traffic still runs NSA, which remains very fast with a strong 4G anchor.
Why are uploads so much lower than downloads?
On NSA, uplink can be constrained by the 4G anchor and RF geometry. In busy areas and on the beach, body blocking and sector load hit uplink first.
Can I rely on airport 5G for video calls?
Usually, yes—but step outside or near windows for better uplink. Terminal interiors prioritise coverage; uplink can be inconsistent at peak times.
How do I find mmWave in the CBD?
Look for small cell nodes on streets with clear sightlines (e.g., around Martin Place). Stand in open air, keep the phone unobstructed, and face the node. Small moves matter.
Does an eSIM affect speed?
No—what matters is network, band, coverage, device modem and load. eSIM is just the provisioning method. Local profiles generally beat roaming for latency.
I’m visiting Bondi at sunset—any hacks?
Test at the seawall rather than on the sand, avoid crowds blocking line‑of‑sight, and try a backstreet near Campbell Parade for a stronger sector and better uplink.

Bottom line

Sydney’s 5G delivers excellent real‑world performance where it counts, with mmWave party tricks in the CBD, dependable mid‑band almost everywhere, and predictable beach‑front variance driven by geometry and crowds. SA is emerging and helps with jitter, but NSA still wins peak throughput today. Plan your calls and uploads around line‑of‑sight and time‑of‑day, and you’ll have a smooth trip.

Next step: planning more stops after Sydney? Start with our city playbooks and regional eSIMs on Destinations.

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

How Much Data Do You Need Abroad? 7/14/30-Day eSIM Calculator

Travelling with an eSIM should be simple, but picking the right data size can be confusing. Buy too little and you’re hunting for top-ups mid-trip; buy too much and you pay for gigabytes you never use. This guide gives you a practical, traveller-first way to answer the question: how much data do I need? Use our light/standard/heavy presets for 7, 14 and 30 days, or build your own estimate in three minutes. We also share real-world scenarios, data-saving tips, and regional plan pointers.Prefer a handy worksheet? Download our 7/14/30-day eSIM calculator sheet (CSV/printable) from any country page—start at Destinations. If you’re heading to Europe or North America, we’ve linked regional plans to make selection easy. Whether you’re a minimalist traveller who messages and maps, or you hotspot your laptop and stream in HD, you’ll find a clear, conservative number that prevents bill shock and keeps you connected.How much data do I need? The quick answer (presets)Pick the profile that best matches your habits. These ranges include a 10–20% buffer for maps, translation, ride-hailing and background usage.7 daysLight: 3–5 GB (messages, maps, light socials, a few photos)Standard: 7–10 GB (daily socials with occasional video, a few video calls)Heavy: 15–25 GB (regular video, hotspot for laptop)14 daysLight: 6–10 GBStandard: 12–20 GBHeavy: 30–40 GB30 daysLight: 10–15 GBStandard: 20–30 GBHeavy: 50–80 GBDaily budget at a glance: - Light: ~0.3–0.5 GB/day - Standard: ~0.8–1.0 GB/day - Heavy: 2–3+ GB/dayIf you stream HD video, upload lots of media, or tether a laptop, use the “Heavy” band. If you mainly message over Wi‑Fi at your hotel and occasionally use maps on the go, “Light” fits most trips.Build your own estimate (3-minute calculator)1) Choose your travel profile - Light: Messaging, maps, light browsing, minimal video - Standard: Daily socials with some video, a few short video calls, occasional streaming - Heavy: Frequent video/streaming, regular video calls, hotspot/tethering2) Add your daily activities Use these conservative averages: - Messaging (WhatsApp/iMessage/Telegram): 5–20 MB/hour (text and stickers) - Photo sharing: 2–5 MB per photo; 100 photos ~200–500 MB - Web browsing/news: 60–150 MB/hour - Social feed scrolling: 150–300 MB/hour (mixed image/video) - Short-form video (Reels/TikTok): 0.8–2 GB/hour (varies by quality) - YouTube/streaming: - 480p: 300–500 MB/hour - 720p: 0.7–1 GB/hour - 1080p: 1.5–3 GB/hour - Music streaming: 40–150 MB/hour - Video calls (WhatsApp/FaceTime/Meet): 300–600 MB/hour (more for HD) - Maps/ride-hailing/translation: 50–150 MB/day (if not offline) - Email (with occasional attachments): 20–100 MB/day - Hotspot for laptop: highly variable; light work 200–500 MB/hour, heavy browsing/calls 1–2 GB/hour3) Multiply by trip length and add a buffer - Sum your typical day, multiply by days abroad, then add 20% for navigation spikes, uploads and updates.4) Pick your plan size - Choose the next plan size above your estimate. Ensure the plan supports top-ups or add-ons if you run low.5) Optional: get the sheet - Download the calculator sheet from any country plan page under Tools—start at Destinations.Pro tip: If your usage varies (city days vs. beach days), average your “busy” and “quiet” days to avoid overbuying.Real-world scenarios (what actually works)4-day city break (Light)Usage: maps/ride-hailing, messaging, 1 hour/day social, minimal videoEstimate: ~350 MB/day × 4 = 1.4 GB, +20% = ~1.7 GBPick: 3–5 GB to be safe. Country plans such as Esim France, Esim Italy or Esim Spain often start at 3–5 GB.10-day mixed sightseeing (Standard)Usage: 1–2 hours/day social (some video), a couple of 20-min video calls, maps dailyEstimate: ~900 MB/day × 10 = 9 GB, +20% = ~11 GBPick: 12–15 GB. For multi-country, see Esim Western Europe.14-day work-and-wander (Heavy)Usage: 1 hour/day HD video calls, hotspot for email/docs, light streamingEstimate: ~1.8 GB/day × 14 = 25 GB, +20% = ~30 GBPick: 30–40 GB. If you’ll enter the US or Canada, check Esim North America.30-day US road trip (mix of Standard/Heavy)Usage: daily navigation, frequent social uploads, 3–4 hours/week streaming, occasional hotspotEstimate: ~1.2 GB/day × 30 = 36 GB, +20% = ~43 GBPick: 50 GB+ to avoid mid-trip top-ups. See Esim United States.Make any data plan go further (pro tips)Download offline maps for regions you’ll drive/walk in.Set streaming to 480p/Auto on mobile; save HD for Wi‑Fi.Turn off auto-backup of photos/videos on mobile data; allow on Wi‑Fi only.Disable automatic app updates on mobile data.Use “Data Saver/Low Data Mode” on iOS/Android and in social apps.Cache playlists/podcasts on Wi‑Fi.Set a daily data warning (e.g., 500 MB, 1 GB) in system settings.Prefer Wi‑Fi in accommodation and cafés for uploads, cloud sync and big downloads.If you hotspot, update your laptop to “metered connection” to stop background syncs.Region and plan pointersEurope in one trip: Esim Western Europe covers popular countries without swapping plans.Single-country Europe: Start with Esim France, Esim Italy or Esim Spain for focused trips.USA only: Get a domestic bundle via Esim United States for best local performance.Multi-country US/Canada/Mexico: Choose Esim North America to avoid SIM juggling.Team travel or remote workforces: Centralise budgets and usage with For Business.Travel creators, agents or resellers: Access tools, assets and co-branded links via the Partner Hub.Checklist before you flyInstall your eSIM while you still have reliable Wi‑Fi.Set “Low Data Mode/Data Saver” and disable background app refresh on mobile data.Pre-download:Offline maps for cities/regionsTranslation packsPlaylists and shows for transitIn social apps, set “Data saver” and restrict auto-play to Wi‑Fi.Turn off mobile data for cloud photos/backups.Set a daily data warning and roaming data cap (Android) or mobile data limit (third-party app on iOS).FAQ: how much data do I need on holiday?How much data does Google Maps use on a trip?Typical navigation with occasional searches is 50–150 MB/day if you don’t download offline maps. Offline areas reduce this to near-zero aside from search and traffic updates.Is “unlimited” data worth it while travelling?Often not. Many “unlimited” plans have fair-use thresholds and speed caps. A well-sized 20–40 GB plan is enough for most 2–3 week trips, with better speeds and price per GB. Go unlimited only if you stream a lot or tether daily.Do WhatsApp and iMessage use much data?Texts and stickers are tiny (a few MB/hour). Voice calls use ~0.5 MB/min; video calls 5–10 MB/min. Daily messaging plus a short video call can still fit in 300–500 MB/day.Should I buy one regional plan or separate country plans?If you’ll cross borders, regional plans like Esim Western Europe or Esim North America are simpler and often cheaper than juggling multiple country eSIMs. Single-country trips may be best served by local plans such as Esim France, Esim Italy or Esim Spain.Can I use my eSIM for hotspot/tethering?Usually yes, but it can burn data quickly. A light work hour via hotspot can use 200–500 MB; HD video calls or updates can push 1–2 GB/hour. Check plan details for any tethering restrictions.What happens if I run out of data mid-trip?Most plans allow top-ups or add-ons. Set a daily warning, and if you’re trending over budget, lower streaming quality and delay large uploads to Wi‑Fi before you buy extra data.Next stepStart with your destination, pick your trip length, and choose a plan that matches your profile. Explore plans now at Destinations.

30 Oct 2025

Wholesale Pricing & Forecasting: Volume Tiers, Commitments, and Margins

Wholesale pricing for eSIM is different to retail: you’re negotiating capacity, not just buying SKUs. That means tiers, commits, and forecasting accuracy decide your margin as much as your selling price. In this guide we unpack the mechanics of wholesale pricing eSIM: how tier schedules actually calculate, what “hard vs soft” commitments mean in practice, and how to build a forecast tied to travel seasonality and itineraries data. You’ll find worked breakeven maths, practical demand-shaping tactics that don’t hurt the traveller experience, and checklists you can run every month. We’ll also show where regional packs such as Esim Western Europe or Esim North America help you reach volume tiers faster—while still giving travellers the coverage they expect across popular routes like the US, France, Italy and Spain. If you’re a reseller, OTA, fintech, or device brand building travel connectivity, use this as your operating playbook.What drives wholesale pricing for eSIM?Wholesale price per GB (or per bundle) is set by a few levers:Volume tiers: lower unit costs kick in above stated thresholds (e.g., 10k, 50k, 100k GB/quarter).Commitments: price discounts in exchange for a minimum draw (soft commit) or pay-or-take (hard commit).Geography and roaming policy: single-country vs regional vs global; in-country vs roaming partners.Validity and pack size: shorter validity and micro-packs cost more per GB; larger bundles cost less.Quality-of-service: 4G/5G access, throttling thresholds, and fair-use policies.Commercial terms: price hold periods, FX currency, payment terms, and promotion allowances.Pro tip: - Aggregate demand into broader regional products (e.g., Esim Western Europe) to climb tiers faster without sacrificing the traveller experience.Tier schedules that actually workA tier schedule defines your unit cost as volume increases within a time window (usually monthly or quarterly). There are two common models:1) Stair-step (all units at the tier rate once you pass the threshold)2) Marginal (each tier’s rate applies only to the units within that tier band)Sample stair-step schedule (quarterly, illustrative USD):Tier 1: 0–9,999 GB = $4.50/GBTier 2: 10,000–49,999 GB = $3.90/GBTier 3: 50,000–99,999 GB = $3.30/GBTier 4: 100,000+ GB = $2.80/GBBlended cost calculation example (stair-step): - If you end the quarter at 12,000 GB, all 12,000 GB price at $3.90 → Blended = $3.90/GB. - At 9,800 GB you’re stuck at $4.50/GB. Missing the 10k tier by 200 GB costs: 9,800 × ($4.50 − $3.90) = $5880.Marginal schedule example: - First 10,000 GB at $4.50, next 40,000 GB at $3.90, etc. - Blended = (10,000 × $4.50 + 2,000 × $3.90) / 12,000 = $4.40/GB.Pro tips: - Ask which model applies; your demand-shaping tactics differ materially between stair-step and marginal. - Request a end-of-period “true-up” option if you’re near a threshold; it reduces expensive shortfalls.Commitments: soft vs hard (and why it matters)Commitments exchange predictability for price. The fine print decides your risk.Soft commit (drawdown): You commit to a volume window (e.g., 30 TB/quarter). If you fall short, you may roll forward a portion or pay a gap fee.Hard commit (take-or-pay): You pay for the committed volume whether you consume it or not, usually for deeper discounts.Floors/ceilings: Some contracts allow ±10–20% variance without penalty.Price protection: The wholesale rate is held for a fixed term; important in volatile FX or roaming markets.Carryover and expiry: Clarify if unconsumed volume can roll to the next period.Worked example (quarterly): - Commit: 30,000 GB at $3.60/GB (hard). Retail ASP blended = $5.40/GB. - If you consume 27,000 GB, you still pay for 30,000 GB. Effective cost per consumed GB = (30,000 × $3.60)/27,000 = $4.00/GB (margin shrinks). - If you hit 35,000 GB and a “best-tier-applies” clause exists, you may benefit from the 50k band if the schedule is marginal and pro-rata true-up is allowed.Checklist before you sign: - Commitment type and tolerance band - Tier model (stair-step vs marginal), and true-up mechanics - Price hold duration and currencies accepted - Carryover rules and expiry dates - Penalties, promo allowances, and support SLAsForecasting that matches travel seasonalityTravellers don’t move in straight lines; your forecast shouldn’t either. Anchor your plan to itineraries and known peaks.Key inputs: - Bookings and search data by corridor (origin–destination) - Seasonality curves (e.g., Europe peaks Jun–Sep; US peaks around spring break and summer) - Product mix by destination: Esim United States, Esim France, Esim Italy, Esim Spain, and regional packs like Esim Western Europe or Esim North America - Attach rate assumptions by channel (web, app, checkout upsell)Step-by-step: from itineraries to SKU forecast1) Map corridors and destinations- Use your booking data and reference coverage in Destinations to build a top-20 route list.2) Build monthly arrival curves- Distribute expected travellers by month using last year’s arrivals and events calendars (festivals, trade shows, school holidays).3) Set attach rate per corridor- Example: OTA checkout upsell 8–12%, post-booking emails 3–5%, in-app for existing users 15–25%.4) Choose pack mix by stay length and use- City-breakers: 3–5GB; road-trippers: 10–20GB; remote workers: 20–50GB regional packs.5) Convert travellers to data volume- Travellers × attach rate × average GB per plan = monthly GB demand.6) Layer variance buffers- Apply ±15% range, then choose a commit that your p50–p60 scenario can reliably hit.Pro tips: - Bundle single-country with regional coverage to capture multi-country itineraries (e.g., France–Italy–Spain) under one plan and push volume into a single tier. - Use early-bird promotions to pull demand from month 1 to month 0 when you’re close to a tier.Breakeven and margin maths made simpleKeep a small set of formulas in your pricing sheet:Blended wholesale cost per GB = Weighted average of tiers and/or commits.Revenue per GB (implied) = Average selling price (ASP) per plan ÷ Average consumed GB per plan.Gross margin % = (Revenue − Cost) ÷ Revenue.Worked example (USD, illustrative): - You sell a 10GB US plan at $18 ASP. Average actual consumption = 7.5GB (some users underuse). - Implied revenue per GB = $18 / 7.5 = $2.40/GB. - If your blended wholesale cost is $1.85/GB, gross margin = ($2.40 − $1.85) / $2.40 = 22.9%.Breakeven ASP targeting: - Target ASP = Blended cost per GB × Expected consumption per plan ÷ (1 − Margin target) - With $1.85/GB cost, 7.5GB consumption, 25% margin: Target ASP = 1.85 × 7.5 ÷ 0.75 = $18.50.Pro tips: - Monitor “consumption/entitlement ratio” (used GB ÷ plan GB). Improving utilisation by 0.5GB can lift margin more than a 20c price change. - FX hedging: if you buy in EUR and sell in USD/GBP, set an FX buffer in costs.Demand shaping that respects travellersThe goal: reach better tiers without compromising experience.Tactics that work: - Regional-first catalogues: Promote Esim Western Europe to travellers visiting France–Italy–Spain; promote Esim North America for US–Canada–Mexico trips. - Plan-size rationalisation: Offer 5GB/10GB/20GB core sizes; prune slow-moving variants that fragment volume. - Time-bound promos: Run 5–10% discounts late in the month/quarter if you’re within 5–8% of the next tier. - Value add-ons: Free hotspot allowance or extended validity instead of deep price cuts; protects ASP. - Tie-in at booking: Highlight coverage on destination pages like Esim France or Esim Italy within itineraries flows.Guardrails: - Keep throttling and fair-use transparent; never silently degrade service to squeeze margin. - Cap promo frequency to avoid training customers to wait for discounts.Risk management: variance and buffersEven great forecasts miss. Design controls:Safety commit: Contract at 60–70% of p50 demand; use spot or overage for spikes.Spillover product: If a country SKU risks overage, route customers to a regional SKU with headroom.Threshold alerts: Daily run-rate vs tier threshold; auto-trigger promotional levers when gap <8%.SLA monitoring: Latency and attach success; quality issues can tank conversion and strand volume.Scenario planning checklistRun this monthly in the run-up to peak season:Update arrivals and attach-rate assumptions by corridorRefresh tier attainment model and true-up statusRecalculate blended cost and breakeven ASPIdentify SKUs to promote for tier climbingValidate inventory/commit headroom by regionConfirm FX impact on costs and planned pricesPrepare switchbacks (alternative SKUs) if a network degradesCase example: Western Europe summer peakContext: - You expect 42,000 travellers across France–Italy–Spain June–August. - Attach rate target: 12% via checkout plus 4% in-app = 16% overall. - Average plan: 10GB regional.Forecast: - Travellers × attach rate = 6720 plans. - Entitlement volume = 6720 × 10GB = 67,200 GB. Expected consumption ratio 0.75 → 50,400 GB used.Commercial move: - Instead of three separate country SKUs, concentrate on Esim Western Europe to consolidate volume and achieve the 50k GB tier. - Offer a June pre-departure promo to pull 5% of July demand forward if you’re short of the threshold. - Feature destination coverage pages in your content stack: Esim France, Esim Italy, Esim Spain.Outcome: - Blended wholesale rate improves by $0.40/GB at the higher tier, translating to ~$20k extra gross margin over the quarter without raising retail prices.Operational mechanics and KPIs to trackInstrument these weekly:Activation success rate and time-to-first-byteAverage consumed GB per plan and consumption/entitlement ratioTop-ups per 100 activationsOverage and throttling incidenceRefund rate and support contact rateTier attainment tracker (run-rate vs thresholds)Channel attach rate trends (checkout vs post-booking vs in-app)Pro tip: - Tie a real-time “tier gap” widget into your merchandising engine to auto-boost regional SKUs when you’re near thresholds.How Simology helps partners executeCoverage and planning: Use Destinations to align catalogue with where travellers actually go, from the Esim United States to multi-country options like Esim North America.Commercial tooling: Consolidate commits across country and regional SKUs, with clear stair-step vs marginal models and end-period true-up options where available.Data and dashboards: Forecasting modules that ingest itineraries and seasonality; alerts for tier thresholds and SLA anomalies.Partner enablement: Bulk provisioning, voucher flows, and flexible APIs via the Partner Hub.B2B support: Contracting, FX-aware pricing guidance, and joint promotional planning—see For Business.FAQ1) What is “wholesale pricing eSIM” in plain terms?It’s the rate you pay for eSIM data capacity at scale, influenced by volume tiers and commitments, not just per-plan retail price. Your margin depends on hitting thresholds and managing consumption.2) Should I choose soft or hard commitments?If your demand is seasonal or volatile, soft commits with limited carryover reduce risk. If your forecast is dependable and you can aggregate demand (e.g., regional SKUs), hard commits can unlock better rates.3) How do I avoid missing a tier by a small margin?Monitor run-rate daily. In the final week, promote regional packs (e.g., Esim Western Europe) or run a limited discount. Ask for end-of-period true-up rights when negotiating.4) What pack sizes maximise margin without harming travellers?Offer a tight set (5GB, 10GB, 20GB). Use data on average consumption; if 10GB users typically consume 7–8GB, pricing can be set to a healthy margin while keeping fair value.5) Do regional eSIMs hurt user experience?No—done right they improve it. Travellers moving between, say, France–Italy–Spain avoid swaps, and your volumes consolidate to better tiers. Highlight coverage pages like Esim Italy to build confidence.6) How often can wholesale tiers or prices change?Typically quarterly, with a price-hold clause. Mid-term adjustments can occur with FX swings or network changes; build 3–5% contingency into your margin model.Next step: Explore tooling, APIs and commercial options in the Simology Partner Hub to structure your tiers, forecast with seasonality, and protect margins.

30 Oct 2025