How to check your eSIM data usage

Every phone bill you have ever received was a metering report. Prepaid travel data works the other way round: you pay once, the network counts down against what you bought, and nothing is ever sent back to you about it. On an anonymous store there is a second reason, and it is structural rather than a missing feature.

• Your order page is a receipt, not a dashboard. It shows the country, the pack size, the date, the price and whether the profile is active — the facts of the purchase, not a running total of your traffic.
• There is no account for usage to attach to. An order here is a random reference with no name behind it, and a per-user consumption history is exactly the kind of profile the whole design exists to avoid keeping.
• The network still counts, of course. A pack has to stop at 3 GB somehow, so volume is metered where the traffic actually flows. What does not exist is a copy of that number sitting next to your identity.

iOS keeps a running total for mobile data, and it is the most misread number in the settings app — not because it is wrong, but because nothing on the screen tells you when it started.

1. 01
   Open Settings, then Cellular

   Called Mobile Service or Mobile Data depending on where your phone thinks it lives. Your installed plans are listed at the top of that screen.

2. 02
   Scroll down to Cellular Data

   Below the plan list sit Current Period and, separately, Current Period Roaming. Under those is a per-app breakdown, sorted with the biggest consumer first.

3. 03
   Read the roaming line too

   A travel profile is a foreign-issued line registering on a local network, so its traffic usually lands in the roaming total. That makes it a useful cross-check rather than a guarantee — the arrangement behind a given profile decides how it reports.

4. 04
   Find the reset date at the bottom

   The very last item on the page is Reset Statistics, and beneath it the date it was last tapped. If that date is two years ago, the number above it is two years of data.

The fix is one tap, and the right moment for it is the subject of a later section — because when you reset it matters considerably more than that you did.

Android measures the same thing but frames it as a billing cycle, which suits travel better than it sounds: unlike iOS, you get to say when the cycle begins, and you get a hard stop at the end of it.

1. 01
   Settings, then Network & internet

   On Pixel and most stock-Android phones the path is Network & internet › SIMs, then your travel line. Samsung files it under Connections › Data usage. The label differs on every skin; the screen underneath is the same one.

2. 02
   Open App data usage

   You get a graph across the current cycle and a per-app list beneath it. Tapping an app splits its foreground and background use, which is how you catch something spending while you are not looking.

3. 03
   Move the cycle start day

   Under Data warning & limit you can change the day the cycle resets. Set it to the day you land and the graph becomes a chart of your trip instead of a chart of the calendar month.

4. 04
   Set a warning, and then a limit

   A warning notifies you at a threshold. A limit is a different thing and a better one: at the number you choose, Android switches mobile data off by itself. It is the closest thing to a safety net either platform offers.

Two minutes at home buys a number you can trust for the whole trip. Done on arrival instead it still works — you simply lose the first day to a counter that had not started yet, which is the day you can least afford to be guessing.

A data counter is not one honest number. It is a sum of everything the operating system decided to attribute to mobile data, and the edges of that decision are where the surprises live.

At some point you will compare what your phone says you used against what the pack had in it, and the two will not match. Neither is broken. They are counting in different places, and the network is always counting a little more.

Once the counter is trustworthy, using it well takes about ten seconds every few days. There are two sums, and between them they answer every question worth asking mid-trip.

1. 01
   Divide what is left by the days left

   Gigabytes remaining over nights remaining is your daily budget. If it sits comfortably above what you have actually been spending, stop thinking about it — arriving at that conclusion is the entire point of doing the sum.

2. 02
   Check yourself at the midpoint

   Half the trip should have spent roughly half the pack. Sixty per cent is fine. Eighty per cent on day three of six is a signal, and it is nearly always one app rather than a lifestyle.

3. 03
   Decide early rather than at zero

   If the projection says you will run short, buy the second pack while the first is still working. Deciding with a live connection in your hand is a different experience from deciding without one.

4. 04
   Screenshot before you change anything

   If you are about to reset the counter or switch packs, capture the total first. It is the only record that exists, and there is no server-side copy to fall back on.

The other half of the arithmetic is the calendar, and the data counter will never show it to you. A pack ends at whichever counter empties first — the gigabytes or the thirty days — so a 10 GB pack on a five-day trip is not generosity, it is 7 GB thrown away on day thirty. Watching only your usage answers half the question.

When the daily budget refuses to add up, the per-app list settles it in about fifteen seconds. It is sorted by consumption, and the answer is essentially always in the top three.

• Photo and cloud backup. A weekend of holiday photos is several hundred megabytes going up while the phone sits on a bedside table. Restrict it to Wi-Fi once and the problem is gone permanently.
• Feeds that autoplay video. Scrolling costs almost nothing; the video that starts playing underneath your thumb costs a great deal. It is one setting per app, and it is worth hunting down all of them.
• Podcast and app-store auto-download. Both are built to fetch quietly on any connection they can find. Both have a Wi-Fi-only toggle that most people have never opened.
• The system itself. A major OS update is measured in gigabytes and has no idea what your connection costs unless you tell it.

Tethering is the fastest way to empty a travel pack, and the counter only shows you why after the fact: everything the laptop did arrives as a single line item with no breakdown behind it. A phone browses like a phone. A laptop browses like a desktop and updates like a data centre.

• It comes out of the same pack. There is no separate hotspot allowance and no second meter — one pool, spent by whatever happens to be connected to it.
• Mark the connection as metered on the laptop. Windows has a metered-connection switch per network; macOS has Low Data Mode in the Wi-Fi details. Both stop background updates from treating your pack as home broadband.
• Quit the sync clients before you connect. Cloud drives, photo libraries and backup tools reconcile the instant they see a network, and they will happily reconcile several gigabytes of it.

A prepaid pack does not warn you. It does not slow down first and it does not send a message. It simply stops, while the status bar carries on showing full bars because the phone is still perfectly registered on the local network — signal and data being two entirely different things.

1. 01
   Recognise the symptom

   Full bars and nothing loading is the signature of an ended pack, not a broken one. Check the counter and the dates before you start troubleshooting anything at all.

2. 02
   Buy the next pack from your balance

   A funded balance makes this one tap and no invoice. It is a fresh pack with its own QR and its own thirty days, rather than an extension of the one that ended.

3. 03
   Install it calmly, on Wi-Fi where you can

   The new profile installs exactly as the first one did. Leaving the finished one in place until the replacement is working costs you nothing.

4. 04
   Keep one thing offline, always

   An offline map of the city, the hotel address and the return booking, saved before you leave. It turns a dead pack into an inconvenience instead of a problem.

If the counter says there is data left and the thirty days have not run out, then this is a genuine fault rather than an ending, and faults have a short list of causes. The troubleshooting checklist opens with data roaming, which is the culprit far more often than anything else on it.

It is worth closing on what that number actually is, because a per-app usage history is a remarkably detailed object: which apps you use, when you use them, how much you send and how much you receive. It is a behavioural diary, and it lives in exactly one place.

• It stays on the device. The per-app breakdown is compiled locally, because only the phone can see which app opened which connection. None of it is reported back to the store the pack was bought from.
• There is no usage history on your order page. Not withheld, not hidden behind a login — simply never assembled, because there is no identity for it to be assembled against.
• Volume is still known where the traffic flows. A pack has to stop at its limit, so the network counts bytes by necessity. What it counts is a volume attached to a profile, not to a person.