Battery and data on the day you run or cheer

On race day, battery matters more than data

People running a marathon abroad worry about data, but the thing that runs out first is almost always the battery. Race day combines three heavy drains: GPS running continuously for hours, live location shared with supporters, and a congested network that makes the phone raise its transmit power to hold a cell. All three run at once for the whole time you are on the course.

• Turn off automatic photo backup and unrelated app sync the night before
• Lower the location update frequency if the app allows it — once a minute is plenty for tracking
• If a watch records the run, let the phone do nothing but communicate — far cheaper on power
• Keep a small power bank in the bag drop so you can charge right after finishing

The course and the busiest cells

A big race gathers tens of thousands of people at the start at the same minute, then moves that crowd to pile up again at the finish. Those two points are the worst network of the day — and happen to be the two points where everyone most wants to call each other. The middle of the course is usually better because runners spread out, though pockets with dense spectator crowds slow down too.

What the supporters need to arrange

Supporters often have the harder job: moving between points on the course using public transport that road closures have disrupted, watching a live tracker, and working out whether they can reach the next spot in time — all on one phone whose battery must last until evening. The most effective preparation is choosing the viewing spots in advance and learning the routes between them the night before.

1. 1Days before: read everything the organiser publishesThe route, road closures, wave start times and bag-drop rules are all set by the organiser and differ every year. Read them on the event's official website and nowhere else.
2. 2The night before: strip the phone downCharge fully, turn off automatic backups, stop sync for apps you will not use, and download offline maps of the area around the course.
3. 3The night before: agree meeting points with supportersPick something easy to see that is not the spot everyone picks, and agree a backup time in case the finish comes earlier or later than expected.
4. 4Race morning: send the important messages before the pensSend your bib number, expected start time and tracking link to supporters before you walk into the densest part of the day.
5. 5After finishing: charge first, upload laterCollect the power bank from the bag drop and charge straight away; leave photo and video uploads until you are back on Wi-Fi.

What race day actually consumes

Location sharing uses less data than people assume, because a set of coordinates is tiny. What actually consumes is the video and photos exchanged during the day, and supporters reloading a results page over and over. The figures below are planning estimates, not measurements from your own device.

• Four hours of live location sharing: roughly 50–150MB
• A supporter with maps and a tracker open all day: roughly 1–2GB
• Ten short video clips to a family group: roughly 200–600MB
• Uploading the day's media in the evening: roughly 1–3GB if done on mobile data

Common sizing mistakes for a runner heading abroad

The most common runner's mistake is sizing data only for the race day itself, forgetting that the day before means collecting the bib at the expo — usually somewhere separate from the accommodation and just as map-heavy. Another is assuming supporters will use little data because they are only standing and watching, when in fact a supporter moving along the course typically uses more mobile data than the runner, who mostly just runs GPS in the background while a supporter has maps open continuously. A third is not allowing for the day after the race, when many people want to upload celebration photos and make a long call home, only to find there is barely any data left because most of it went on tracking during the race itself.

When to buy a plan before you have a confirmed race entry

Many large races use a lottery or a waitlist, so a lot of people do not know for certain that they have a place until close to the event. The practical approach is to keep accommodation and flight bookings separate from the data plan purchase: book the room and flights against the published event date, and choose a data plan that only starts counting once you activate it yourself, so an expiry tied to the purchase date is not a worry while your place is still unconfirmed.

If you are a supporter planning around a runner, wait until the runner confirms a place before booking accommodation near the course — rooms close to the start and finish tend to fill quickly once lottery results are announced. Buy the data plan shortly after that, leaving enough time to install and test it before race day itself.

The expo and the day before eat more data than expected

The days before a race often get skipped in data planning, even though they are just as map-heavy as race day itself. Bib collection at the expo usually happens in a large convention centre away from the accommodation, reached by several legs of public transport. Runners often walk part of the course on their own during this time and photograph directional signage to study later. All of this happens in an unfamiliar city, which can mean opening maps more often than on race day itself — race day has marshals and signage pointing the way the whole route, but the day before you are finding your own way.

Watching a big match without running yourself

People who fly abroad to watch football or another major sport hit a slightly different problem from a runner: there is no start and finish spread out over a course, just one stadium that tens of thousands enter and exit within a short window, both before kick-off and right after the final whistle. The worst stretch is usually not during play, when people sit still and use less data, but the thirty minutes right after the game ends, when the whole stadium picks up a phone at once to check results, message people and order a ride.

Digital tickets and the risk right at the gate

Many large sporting events have shifted to digital tickets that load through an app or the phone's wallet, and the ticket gates usually sit exactly where the day's crowd is thickest. If a ticket has not been downloaded ahead of time and needs to load live at the gate, the risk of the network being too slow to keep up with a moving queue is higher than people expect. The practical response is opening the ticket and saving a screenshot as backup before leaving the accommodation, even if the ticket app already supports offline use — a second layer of backup costs nothing at a moment where a mistake is hard to fix.

Finding friends in a crowd once tens of thousands leave at the same moment

The hardest stretch of the day is often not inside the venue but the moment tens of thousands of people leave it at once, all heading the same direction out of the stands. The network around the exits peaks at exactly the moment everyone most wants to reach someone else. What actually works is agreeing on a clear, memorable meeting point beforehand, such as a numbered gate or sign, rather than relying on a live pin or a verbal description, and agreeing before going in that if contact fails within a set amount of time, everyone heads to that point instead of wandering around looking for each other.

Live-streaming the result for people back home to watch along

Some people watching a live event want to shoot a short video or run a live stream for family back home to watch along, and uploading live video needs a far steadier upload speed than ordinary browsing does, making it one of the heaviest data activities of the whole event day. If you intend to stream a key moment, test the upload speed before that moment actually arrives, since speeds tend to drop hard right when everyone around you is doing the same thing at once, and keep a backup plan of recording the video to send later if live streaming genuinely does not work at that moment.

Following live results in real time while waiting for a friend to cross the finish line

People cheering on a friend or family member running a marathon often leave a results-tracking app open for the whole event, to see which point of the route the runner has reached and where to head to wait next. These apps typically refresh position data every few minutes and keep pulling data continuously even when the screen isn't being actively watched, so leaving one open for several hours in a row can use more data than expected. Near the start and finish areas, where crowds are thickest, connection speed can dip temporarily, making the app refresh slower than usual. It helps to close the app when not actually checking it, to save both data and battery while waiting.

Browse all eSIM plans