How Much Mobile Data Does Live Streaming a Run Use? 5K to Marathon

You want your family to watch your first half marathon live, but one question keeps coming back: will I run out of data halfway through? The good news is that you can work this out to the megabyte. No guessing, no vague "video uses a lot of data".

In this guide you get one simple formula, a ready table for 5K, 10K, half marathon, marathon and a long bike ride, and practical ways to fit a live stream into your plan.

The one formula you need

Video data usage depends on one number: the bitrate, which is how much data your phone sends every second. It is measured in megabits per second (Mbit/s). Data plans, on the other hand, are measured in megabytes and gigabytes, and 1 byte is 8 bits.

So the formula is:

data (MB) = bitrate (Mbit/s) × time (s) / 8

One minute at 1.5 Mbit/s: 1.5 × 60 / 8 = 11.25 MB. One hour: 1.5 × 3600 / 8 = 675 MB, or about 0.7 GB.

You can use this for any stream as long as you know its bitrate. Resolution alone (720p, 1080p) does not tell you how much data you will use. Bitrate does.

What different quality levels cost

On top of that comes a small overhead: audio, GPS data and network packet headers. That adds a few percent, not hundreds of extra megabytes.

How much data a BEON.RUN stream uses

In a BEON.RUN live stream the video goes up to 720p and the bitrate is capped at about 1.5 Mbit/s. That is a ceiling, not a fixed value. When the signal gets weaker, the quality lowers itself automatically, because for a runner a smooth stream matters more than a sharp one.

In practice:

• at full quality: about 11 MB per minute and at most roughly 0.7 GB per hour,
• on a weaker signal: noticeably less, because the bitrate drops,
• without the camera (GPS only): just a few MB per hour.

Why does GPS use so little? A position is a handful of numbers (latitude, longitude, accuracy, time) sent every few seconds. Even several hours of tracking add up to a fraction of a single minute of video.

Table: data for a 5K, 10K, half and full marathon

The numbers below assume full quality (1.5 Mbit/s, so 11.25 MB per minute) and typical amateur finish times. Values are rounded. This is the worst case: camera on the whole time and a good signal.

How to read it: with a 10 GB plan, a marathon with the camera on all the time takes between a quarter and a third of it. With 5 GB it takes most of it. GPS-only tracking makes no real difference to your plan.

On the FREE plan a stream lasts up to 30 minutes. At the quality cap that is about 340 MB, which fits into even a small plan. Longer streams come with PREMIUM and PLATINUM, see BEON.RUN plans for details.

Work out your own run in 30 seconds

You do not need to remember the table. One number is enough: about 11 MB for every minute of video at full quality.

Example: you plan a half marathon in 2:05, which is 125 minutes. 125 × 11.25 MB = about 1.4 GB. Add a buffer for a slower day and call it 1.5 GB. If the camera is on only for the first 10 and the last 15 minutes, that is 25 × 11.25 MB, about 280 MB.

It works the other way too: with 2 GB left on your plan, divide 2000 MB by 11.25 MB. You get about 177 minutes, just under 3 hours of full quality video.

What about the people watching?

A common misunderstanding: "I have 15 viewers, so I will use 15 times more data." You will not. The runner's phone sends the video once to the server, and the server distributes it to every viewer. Your usage is the same with one viewer or twenty.

Each viewer downloads the stream on their own connection. If they watch for an hour on a phone using mobile data, they use a similar amount, around 0.7 GB at full quality. If they watch at home on Wi-Fi or on a TV, it does not matter.

It is worth telling this to friends who will follow you from the course on their phones. A good habit for them: watch the video at key moments and check the map in between. We cover how your people can follow you on the day in our first marathon race day guide.

How it compares with social media live video

Live video on popular social platforms works the same way: bitrate is what counts. At similar picture quality, data usage is in the same range, hundreds of megabytes per hour.

The difference is mainly whether the app lets you control quality and whether it lowers it on its own when the signal gets weak. Many platforms aim for the highest possible resolution because they assume stable Wi-Fi. A runner's situation is different: changing signal, constant movement, a new cell tower every few minutes. That is why the 720p and 1.5 Mbit/s cap in BEON.RUN is a deliberate choice for stability.

LTE or 5G: does it change usage?

Data usage does not depend on whether you are on LTE or 5G. At the same bitrate you send the same number of megabytes. 5G does not "use more".

The difference is upload headroom. On strong LTE and on 5G the stream usually holds full quality. On weak LTE, in a forest, in a crowded finish area or in a valley, the bitrate drops and so does usage. Short signal drops do not end the stream: it reconnects, and GPS points recorded in the meantime are sent once the network is back.

And Wi-Fi? There is none on the course. The phone in your pocket or belt runs on mobile data, so your plan is what counts.

Your plan, roaming and races abroad

Before a long stream, do a quick check of your plan.

1. See how much data is left this month. Your carrier's app shows it in seconds. Do it the day before the race, not at the start line.
2. Unlimited does not always mean unlimited. Many plans have a priority data allowance, after which your speed can be reduced when the network is busy. Race day crowds are exactly that situation, so expect lower video quality once you pass the threshold.
3. Racing abroad. Roaming can be expensive or capped, depending on your carrier and destination. Check what your plan includes in that country before you travel.
4. Travel eSIM or local SIM. For destination races a prepaid eSIM data package is often the easiest fix. Buy and activate it before you fly so you are not hunting for a shop on race day.
5. One-off data add-ons. Many carriers sell a data top-up for a few days. For a marathon with the camera on the whole time, it is a sensible safety net.

Camera on only for the moments that matter

The simplest way to save data is not to stream video the whole time. The live GPS map with distance, time and pace works independently of the camera and uses only a few MB per hour.

A sample marathon plan:

• start and first kilometers: video, for the crowd and the atmosphere,
• middle of the course: GPS map only, your people see where you are and your pace,
• last 2-3 km and the finish: video again.

Every minute without video saves about 11 MB. Half an hour of video instead of four hours is the difference between about 340 MB and about 2.7 GB.

The same idea works even better on a bike, where activities last longer. More on that in our article on live streaming your bike ride.

Quick checklist before you go live

• Calculate: run time in minutes × 11 MB = maximum usage at full quality.
• Check your remaining data in the carrier app the day before.
• Abroad: check roaming terms, or get a travel eSIM.
• Decide where you want video and where the GPS map is enough.
• Charge your phone fully and bring a power bank for long efforts.
• Tell your supporters that watching on mobile uses their data, so the map is "cheaper" than video.

Once you know these numbers, live streaming stops being a risk. It is just one more thing you plan before the start, like your gels and your kit.