Dati giornalieri contro dati per l'intero viaggio

Fai prima i calcoli

Stima il tuo uso giornaliero e moltiplica per il numero di giorni. Se un piano a pacchetto di quella taglia costa meno del totale del piano giornaliero, il pacchetto è il miglior acquisto per quel viaggio.

Most eSIM plans set the data allowance in one of two shapes: a per-day quota that resets fresh each day, or a single pooled amount usable throughout the validity without being split by day. Both can add up to the same total figure, but they behave very differently during an actual trip, especially when each day's use is uneven. This page separates the mechanics of the two rather than declaring one universally better.

It is written for anyone comparing two plans with a similar total data figure but a different way of dividing it up. Everything here refers only to the mechanics actually stated on each plan's own page, because the definition of a 'day' and what happens once the quota is exceeded differ from one plan to the next.

How a per-day quota actually works

A per-day quota provides a fixed amount of data for each day, then resets back to that same amount when a new day begins. Whatever remains unused from the previous day does not carry over into the next one, no matter how much was left. This mechanic makes the amount usable each day predictable throughout the trip.

What needs checking clearly is how that specific plan defines a 'day.' Some count from midnight in the destination time zone; others count a rolling 24-hour cycle from the moment the plan was first used. This affects exactly when the quota actually resets, so read that detail on the plan page before planning daily usage.

How a pooled total allowance actually works

A pooled total is a single amount drawn from throughout the plan's validity, not divided into daily quotas. A heavy day simply draws more from the pool; a light day, or one with no use at all, automatically leaves more for the days after it, since there is no daily reset involved.

The benefit is flexibility when daily use is uneven — a first day heavy with live navigation against a day spent entirely at the hotel barely touching data. The point to watch is that heavy use early in the trip can exhaust the pool before the trip ends, with no fresh quota arriving to reset it.

What happens at midnight for each type

For a per-day quota, midnight is the moment the quota always returns to its full amount, regardless of how much was left over the day before. For a pooled total, nothing special happens at midnight at all, since whatever remains simply stays in the same pool continuously until it runs out or the validity ends.

Days spent barely online

A day spent entirely at a hotel, or relying mostly on free WiFi, means that day's per-day quota simply disappears unused, since it does not carry over to the next day. A pooled total keeps whatever was not used sitting in the same pool automatically, leaving more available for another day that needs it more.

Days with unusually heavy use

The first day at a new destination tends to be the heaviest, with constant reliance on live navigation, hailing rides, and looking things up. On a per-day quota, that day may hit its cap sooner than expected and affect use later that same day. On a pooled total, that day simply draws more than usual from the pool without immediately affecting other days, but it does leave the remaining total lower than planned.

Estimating your own usage pattern before choosing

Before choosing either type, roughly sketch out the usage pattern across the trip: are the days similar or quite different from one another? If every day looks alike — mainly maps and chat in a similar amount each day — a per-day quota is usually easier to predict. If heavy and light days clearly alternate, a pooled total is usually more flexible.

1. 1Sort the itinerary into heavy days and light daysMark the days expected to involve heavy navigation or streaming, and the days expected to rely mainly on accommodation WiFi.
2. 2Total up how many days fall into each categoryCount the heavy days and light days separately, to see the actual ratio of usage behaviour across the whole trip.
3. 3Compare that against the quota structure of the plan under considerationIf heavy and light days clearly alternate, lean toward a pooled total. If every day looks similar, a per-day quota usually fits well enough.

Reading the terms for exceeding a daily cap

Each plan handles reaching its daily cap differently. Some throttle speed rather than cutting the connection outright; others cut the connection until a new day begins. Read that condition on the plan page before buying, since it directly affects the experience on a day that ends up heavier than expected.

Reading the terms for a pooled total running low

For a pooled total running low before the validity period ends, the available fix is to check whether that plan offers a top-up option. If it does, adding more can happen without a fresh install. If not, a separate new plan has to be bought to follow on, the same as any other case where data runs out mid-trip.

Mixing both types across a long trip

For a trip running several weeks, some travellers buy a per-day quota plan for a stretch where usage is known to be steady, such as settled time working in a main city, then switch to a pooled-total plan for a stretch where plans are less certain, such as touring through several cities. This matches the quota structure to each stretch's actual usage pattern more closely than using one type for the entire trip.

Switching this way involves buying and installing a new plan every time, the same as any other plan change, so the timing of that switch is worth planning ahead to land while some data still remains on the current one, reducing the risk of a gap in service the same way any other plan change would.

Why the total figure alone is not enough to decide on

Two plans with the exact same total data figure can deliver quite different experiences if one splits it into a per-day quota and the other pools it. A fair comparison always has to look at the structure alongside the total figure, not just the single number and conclude the two plans are equivalent.

Short trips versus long trips: how the fit differs

For a trip lasting only a few days, the difference between the two types is often not very pronounced, since the small number of days means variation between heavy and light days rarely accumulates enough to cause trouble. For a trip running several weeks, that day-to-day variation tends to build up considerably, making the right structural choice matter more to the overall experience than it would on a short trip.

For this reason, a long trip is worth spending more time estimating usage patterns for in advance than a short one, since the accumulated difference across several weeks affects both value and the overall experience more than a trip that wraps up within a few days.

Common mistakes

The table below summarises common symptoms across both types, the likely cause, and what to do, so you can quickly tell whether something is normal plan behaviour or worth contacting the team about.

Planning ahead by estimating your data needs

Whichever type is chosen, estimating the data actually needed per day in advance leads to a better match with your own behaviour, rather than choosing on the total figure alone without looking at how that figure is actually divided up.

The data calculator on the site converts a rough usage pattern — hours spent on live navigation or streaming, say — into an approximate per-day data figure, which can then be compared against the quota structure of the plan under consideration far more precisely than guessing by feel.

• Whether this plan is a per-day quota or a pooled total, checked directly on the plan page
• How this specific plan defines a day
• What happens on reaching the daily cap, or as a pooled total runs low
• The rough number of heavy days and light days across the trip
• Whether a top-up option exists, in case the allowance runs low before the trip ends
• The trip's total length, since a long trip feels the effect of the wrong choice more than a short one does

Estimate the data needed for the whole trip

Sfoglia i piani per destinazione