Map the plan to a network
The feed or an owner-reviewed record must name the local network for the exact destination. Branding and coverage maps are not enough.
Plan evidenceSpeed evidence, not speed promises
How we estimate eSIM speeds
A useful speed number needs a named network, a dated source and the right label. RoamSonar keeps network estimates separate from traveler measurements so a benchmark never looks more certain than its evidence.
0Mapped plans
0Baseline countries
0Traveler benchmarks
The short answer
An eSIM does not own a radio network. We can estimate context only when a provider names the local network and that exact country-network pair has a reviewed public baseline. If either side is missing, RoamSonar shows “—”.
Evidence pipeline
Three gates before a number appears
Each layer answers a different question. Passing one gate never lets us skip the next.
Attach a sourced baseline
The country-network row needs an expected download figure, source name, public URL and stored update date.
Contextual estimatePublish traveler evidence separately
A provider-country aggregate appears only at five or more moderated, verified reports, with sample size and range visible.
Measured reportsLive benchmark readiness
What RoamSonar can support today
These counts come directly from the production evidence tables. Zero is a valid result, not a blank we fill with a demo number.
Plans with reviewed network mappings
A plan must reach this layer before any country baseline can be attached.
Sourced baseline rows
0 public sources across 0 countries.
Publishable traveler benchmarks
0 verified published reports; each pair still needs n≥5.
The five-report publication gate
Reports one through four can be moderated and retained, but the public provider-country aggregate remains hidden. The fifth qualifying report unlocks publication with its sample size.
1
hold2
hold3
hold4
hold5
eligibleMethodology diagram — not live report progress.
hold2
hold3
hold4
hold5
eligibleMethodology diagram — not live report progress.
Benchmark ledger
Sources and measured reports never share a label
The ledger below is generated from live reviewed rows. It does not contain illustrative networks or sample Mbps values.
Sourced network baselines
No sourced network baselines are published yet.
The estimate column stays “—” until a reviewed row has a network, country, public HTTPS source and stored update date.
Qualifying traveler aggregates
No traveler speed benchmark is published yet.
Verified reports can be stored and moderated, but a provider-country result remains hidden until that exact pair reaches five published samples.
Why results move
Six variables around every speed test
One test is a snapshot of a device, place, network and moment—not a permanent property of an eSIM brand.
Phone and bands
Radio support and modem capability change which network layers a phone can use.
Signal and buildings
Walls, tunnels, distance and indoor coverage can reduce the usable signal.
Local congestion
Busy cells and peak hours can change throughput even at the same location.
Roaming priority
A roaming profile can receive different treatment from a local subscriber.
Route and test server
Traffic path, latency and server capacity influence the reported download rate.
Fair-use throttling
Daily allowances and reduced-speed policies can change performance after a cap.
Read the label
Three speed statements that mean different things
RoamSonar keeps the label beside the number so a ceiling, estimate and traveler result cannot be mistaken for one another.
Provider-published ceiling
A plan term such as an initial or reduced-speed maximum. It is a product limit, not proof that the network will reach it.
Sourced network estimate
A dated contextual baseline for a named network and country, always linked to the public source.
Traveler benchmark
A separate aggregate of at least five moderated, verified reports for one provider-country pair.
Common questions
Speed estimates, without the fine-print fog
Does an eSIM provider control the mobile network speed?
Usually the eSIM provider resells access to a local mobile network. The local network, congestion, roaming priority, phone and location all influence the result.
Is a network baseline a measured result for my plan?
No. A baseline is a dated, sourced estimate for a named network in a country. RoamSonar labels it as an estimate and never presents it as a test of a specific plan.
When does RoamSonar publish traveler speed data?
Only after at least five moderated, verified reports exist for the same provider-country pair. The sample size, arithmetic mean and observed range remain visible.
Why can two speed tests on the same eSIM differ?
Signal strength, phone bands, buildings, congestion, selected network, test server, roaming priority and fair-use throttling can all change between tests.