Total listening hours: the number radio hosting is actually priced on

Almost every radio hosting plan on the market is priced on total listening hours — TLH — and almost every new broadcaster reads the number wrong at least once.

It is not how many hours you broadcast. It is not how many listeners you have. It is the sum, across every listener, of how long each of them listened.

The arithmetic

One listener for one hour is one listening hour. Ten listeners for one hour is ten. Ten listeners for six hours is sixty.

So a station broadcasting 24/7 with an average of 10 concurrent listeners uses:

10 × 24 × 30 = 7,200 TLH per month

With 30 concurrent: 21,600. With 100 concurrent: 72,000.

The station's own broadcast hours never appear in the calculation. A station on air 24/7 with nobody listening uses zero. This is why TLH is what hosts bill on: it is a direct proxy for the bandwidth they will actually deliver.

Why it is misread

Two mistakes, both common.

Confusing concurrent listeners with total listeners. A plan advertising "500 listeners" means 500 *at once*. A station with 40 concurrent at breakfast and 5 overnight might be heard by two thousand different people in a month and never come close to the concurrency cap. Concurrency limits your peak; TLH limits your total.

Assuming an audience is a peak audience. People sizing a plan think of their best hour. TLH is driven by the *average*, and the average is dominated by the long, thin hours — overnight, weekends, the middle of the afternoon. A station with a strong breakfast show and a quiet rest of the day usually finds its overnight audience consumes more of the monthly allowance than the show it is proud of.

That second one cuts both ways. Sessions get longer as a station matures — a listener who leaves you on all afternoon is worth six who dip in — so TLH grows faster than headcount does. Good stations hit their hours limit before they hit their listener limit.

Bitrate multiplies it

TLH counts time, and time is only half of what delivery costs. The other half is bitrate.

One listening hour at 128 kbps is about 57 MB. At 192 kbps it is about 86 MB. So the same 20,000 hours is 1.14 TB at 128 kbps and 1.72 TB at 192.

This is why plans that sell hours also cap bitrate, and why an "unlimited bandwidth" claim next to an hours limit is not generous — the hours limit *is* the bandwidth limit, expressed in the unit that makes it easier to reason about.

Estimate both sides with the listening hours calculator and the bandwidth calculator.

What happens when you run out

Worth knowing before you choose, because the answers differ sharply:

• Overage billing — the stream stays up and you get an invoice. Fine if you watch it; expensive if the spike was a bot.
• Throttling — new listeners are refused while existing ones continue.
• Suspension — the stream stops.
• Downgrade — quality is reduced to stretch the remaining allowance.

The one to check for is the second. Refusing new listeners is the least disruptive to people already listening and the most invisible to you, because your own player is already connected and sounds perfectly fine.

RadioHost Studio warns at 80% of the monthly allowance, which is early enough to do something about it while there is still a month to act in, and enforces at 100%.

Controlling it

Look at where the hours actually go. Almost always the overnight and off-peak hours, because they are long and continuous even when they are thin. That is not an argument for turning them off — an always-on station is the product — but it does mean the savings live there, not in your best show.

Set the bitrate deliberately. Moving from 192 to 128 kbps cuts delivery by a third at a quality difference most listeners cannot identify on the devices they use.

Watch for what is not a listener. Aggregator health checks, uptime monitors, a page that opens the stream on load, and your own studio monitoring all consume hours. A monitor polling every thirty seconds is not a big number; a webpage that autoplays the stream for everyone who lands on it is.

Check session length, not just headcount. If average session length is climbing, your hours will climb ahead of your audience. That is a good problem, but it is one to see coming rather than discover.

Sizing a plan honestly

Take your realistic average concurrent listeners — not the peak, the average across the whole week including 4am — multiply by 720 hours in a month, and add 30% for growth and for the monitoring traffic you have not thought of.

A station with a genuine average of 15 concurrent needs about 14,000 TLH. One averaging 40 needs about 37,000.

For reference, RadioHost Studio's station plan includes 30,000 TLH per month at up to 192 kbps with 500 concurrent listeners, which covers a station averaging around 40 concurrent around the clock.

Frequently asked questions

What is the difference between total listening hours and bandwidth?

TLH counts time; bandwidth counts bytes. Multiply hours by bitrate and you get bandwidth — which is why the two limits always appear together and why a bitrate change moves your bandwidth without moving your hours.

Do I use listening hours when nobody is listening?

No. TLH accrues per listener per hour, so an unattended station with no audience uses none. Broadcast hours are not billed; delivered hours are.

Is 20,000 listening hours a lot?

It supports roughly 27 concurrent listeners around the clock for a month, or a much larger audience concentrated into peak hours. For a station finding its audience it is comfortable; for an established one with continuous listening it is not.

Do smart speakers and aggregators use more hours?

They use the same hours per listener, but they change listening behaviour — a smart speaker left on in a kitchen produces far longer sessions than a browser tab. Stations that get onto smart speakers usually see hours grow faster than listener counts.

Can I reduce hours without losing listeners?

Yes: lower the bitrate, and remove non-listeners — over-eager uptime monitors, autoplaying embeds, studio monitoring left connected overnight. None of that costs you a single real listener.