The !Subcount Command: Put Your Sub Total in Chat

What Does the !Subcount Command Do?

The !subcount command posts your current subscriber total into chat, usually with a milestone attached: “412 subs — 88 to go until 500.” Someone types it, the bot pulls the live number from the platform, and everyone in the room sees the same target at the same time.

That shared visibility is the entire point. A goal that only you can see is a private worry; a goal chat can see is a group activity. Streamers who run subathons, charity pushes or milestone rewards lean on this command heavily, because a viewer who can see that you're twelve subs from a target behaves differently from one who has no idea where you stand.

Technically, !subcount is a step harder to build than most commands, and for a reason worth understanding: subscriber counts are private data. Follower counts are public — anyone can look at your channel page and read them, so a follower command works with no permissions at all. Sub counts are not public anywhere, which means the bot has to be authorised by you before it can see the number. Every setup path below is essentially a way of granting that permission.

The same mechanism gives you the neighbouring commands for free once it's connected: !followcount, !subgoal, and on some bots a !topsub or gifted-sub leaderboard. Set the authorisation up once and add the variations as plain text commands around it.

“Subscriber” Means Two Different Things

This trips up every streamer who works across platforms, and it will make your command's response confusing if you don't handle it. On Twitch and Kick, a subscriber is someone paying a monthly fee. On YouTube, a subscriber is someone who clicked a free button — the equivalent of a Twitch follower. YouTube's paid tier is called membership, and a channel with 40,000 subscribers might have thirty members.

So a !subcount that returns 40,000 on YouTube and 412 on Twitch isn't broken; it's reporting two completely different things. If you multistream, the fix is to be explicit in the wording rather than let the number speak for itself: “412 Twitch subs / 40.2K YouTube subscribers / 31 members” reads correctly to everyone. A bare number reads as a boast on one platform and a rounding error on the other.

There's a second YouTube-specific wrinkle: public subscriber counts are abbreviated, not exact. Above a thousand, YouTube displays a rounded figure, so a command reading the public number can't tell you that you're four away from a milestone — it will keep saying 40.2K for days. If precise counting matters, the number has to come from your own authorised channel data rather than the public display.

Kick sits closer to Twitch: paid subscriptions, exact counts, and a revenue split that makes each one worth noticeably more to you. That changes the tone of the command more than the mechanics — see the Kick chat commands guide for how sub-facing commands land differently there.

Milestones, Subathons and When the Number Helps

A sub count is only motivating when it's close to something. “412 subs” on its own is a statistic. “412 — 88 from the 500 stream” is a call to action, and the gap between those two responses is the entire difference between a command people use and a command people ignore. Always frame the number against the next target, and pick targets close enough to feel reachable: from 412, a 500 goal is a good stream's work, and a 1,000 goal is a shrug.

The command earns its keep hardest during a subathon, where subs extend the clock and chat is actively doing arithmetic about how long you'll be awake. In that format viewers check the number constantly, and having it available on demand saves you from reading it out every ten minutes. If you're planning one, work out your time-per-sub rates before you go live — our subathon timer calculator shows how quickly a generous rate turns a weekend into a week.

Now the honest counterargument: a visible sub count can work against you. On a small or declining channel, a command that answers “7” doesn't rally anyone — it quietly tells every new viewer that nobody else thought this was worth paying for, which is the opposite of the social proof you wanted. There's no shame in the number, but there's no advantage in publishing it either. Below roughly fifty subs, most streamers get more out of a !subgoal command that names the target and the reward without stating the current total.

The same applies after a churn month. Sub counts drop in January, after a big gifted-sub wave expires, and any time you take a break — all completely normal, all visible to chat the moment someone types the command. If you'd rather not narrate that, disable the command temporarily rather than let it broadcast a decline you're not talking about. It's your number and you get to choose when it's on stage.

One last framing tip: pair the count with what subs actually fund. “412 subs — that's what pays for the new camera” converts better than a bare figure, because it turns a vanity metric into a thing your audience is building. Combine it with a !socials command for the people who want to support without subscribing, and you've covered both halves of the ask.