What the stream server actually counts
The stream server counts connections, because a connection is all it can see. When a player opens your listen link, the server starts sending audio and adds one to its count; when the player stops or drops, the count goes down by one. Both engines your station can run on work this way, and both publish the same core counters under slightly different names.
| Figure | Icecast name | SHOUTcast DNAS 2 name | What it means |
|---|---|---|---|
| Listeners now | listeners | CURRENTLISTENERS | Connections open on the stream at this moment |
| Peak | listener_peak | PEAKLISTENERS | The most connections open at the same time |
| Capacity | max_listeners | MAXLISTENERS | The most connections the stream will accept |
| Connections opened | listener_connections (server-wide) | STREAMHITS | A running total of listener connections (Icecast: server-wide; SHOUTcast: per stream, while it is live) |
| Unique listeners | not reported | UNIQUELISTENERS | Unique listener connections; server-wide, a listener on two streams counts once |
| Average time | not reported | AVERAGETIME | Mean age, in seconds, of the connections open now |
On a bare Icecast server the per-mount figures, peak included, reset whenever the encoder disconnects or reconnects. A DJ handover can wipe the raw peak. Keep your history in the control panel, not in the server's own counters.
The four numbers to read, and the limit of each
Most decisions rest on four figures. Each answers one question well and misleads if you ask it another.
| Number | Use it to judge | Do not use it for |
|---|---|---|
| Listeners now | Whether a show has started to draw, and whether the stream is reaching anyone at all | Reach: one person on a laptop and a phone is two |
| Peak | Your busiest moment, and whether you are close to your plan's listener limit | Audience size across a day; a peak lasts a moment |
| Sessions (connections opened) | How many times the stream was started in a period | Counting people; a player that reconnects after a network drop opens a fresh session |
| Listening time | Whether a show holds its audience, compared with the same slot last week | Comparing stations measured by different tools or rules |
Listening time is the figure that tells you most about programme quality. A show with a modest peak and long sessions has a loyal audience; a big peak with short sessions usually means people arrived from a link and left.
Where the figures sit in your control panel
On our HTTPS radio streaming plans every station sees who is tuned in right now and its peaks. What changes between plans is how far back the history goes and how finely it is cut. If a figure in the panel puzzles you, ask the support desk with the date and hour you are looking at.
| Audience feature | Free | Premium | Platinum |
|---|---|---|---|
| Current listeners, exportable as CSV | Yes | Yes | Yes |
| History kept | 7 days | 30 days | 90 days |
| Listening time, plus country, device, app and referrer breakdowns | No | Yes | Yes |
| Figures per show and per playlist | No | Yes | Yes |
| Per-track tune-outs and traffic quality | No | No | Yes |
| CSV exports and scheduled email reports | No | No | Yes |
On Platinum, each listener tunes in through whichever of five cities is closest, and still shows up once in your statistics, whichever city they tuned in from. You do not add the cities together.
A weekly reading routine
Ten quiet minutes once a week beats staring at the live counter. Do it on the same day each week so the comparisons are fair.
- Open the statistics for the last seven days. On Free this is your whole history, so export the current listener list as CSV if you want to keep a record.
- Note the peak for each day and, where the panel shows it, the hour it fell in. Peaks that keep landing in the same hour show you where your audience lives.
- On Premium or Platinum, open the per-show figures. Rank shows by listening time, not by peak.
- On Premium or Platinum, check countries and devices. A rising share on phones is a reason to watch mobile data use; Platinum's extra lighter streams exist for that case.
- On the same plans, look at referrers. They show which website, app or directory sends listeners, so you know where a link is worth keeping up to date.
- Write three numbers in your station log: the week's highest peak, the best show by listening time, the quietest hour. Next week, compare against them.
How to know it worked: after two or three weeks your log shows a pattern you can name, such as an evening peak or a show that holds listeners longer than the rest. If the numbers swing wildly from week to week with nothing changed on air, read the next section before acting on them.
When the numbers look wrong
- Peak fell to zero after a DJ change. A raw Icecast mount resets its counters when the source reconnects. Read the day's history in the panel instead of the server's own peak.
- Sessions are far higher than listeners. Phones on the move lose signal and reconnect, and each reconnect opens a new session. Judge such an audience by listening time.
- The count rises when you open your own website. The player snippet on the service page carries
preload="none", which asks the browser not to fetch audio until play is pressed. If your own player was built without it, page views can open connections. - One listener appears twice. The same person on a desktop and a phone, or in two browser tabs, is two connections. No listener count can tell that two connections belong to one person, so read the figure as plays.
- Listeners stay at zero during a live show. Check that the encoder is connected and the stream is on air before you suspect the statistics. If it is and the count still reads zero, open a support ticket with the time it happened.
Reading the counters at the source
Both engines publish these counters themselves, so a station that also operates a server of its own can read them with no panel at all. Icecast from version 2.4.0 returns its statistics as JSON at /status-json.xsl. The fuller /admin/stats page and the per-mount listener list at /admin/listclients need the admin login, or the mount's own login for the list. SHOUTcast DNAS 2 serves a summary per stream at /stats?sid=1, where the number picks the stream; the listener list with each connection's time and user agent sits behind the administrator page.
Keep the admin login out of shared scripts, dashboards and browser bookmarks other people use. The listener list includes each listener's address, which is personal data; see our privacy policy.
What listener statistics cannot tell you
Server figures describe connections to one stream. They do not say who your listeners are, how old they are, or whether anyone was paying attention while the player ran in a background tab. They do not include people who hear you through another station's relay or a recording.
They are also not ratings. Broadcast audience surveys and streaming counters use different methods, so a number from one cannot be set beside the other. Compare your station with itself, week on week, and the statistics are dependable. When an advertiser asks for evidence, Premium and Platinum include proof-of-airing reports, which show that their spots ran; your listener figures then show the audience around them.
If you also stream video, see live video streaming.