50,000 subscribers — and you can see exactly 200 of them at any moment. Everyone else is invisible. Telegram designed it that way on purpose, and for privacy reasons it makes sense. But for the channel owner trying to understand what's happening with their own audience, it creates a real blind spot.
Why the limit exists
It's not a technical limitation — it's a deliberate privacy decision. If anyone could export a complete member list from any public channel, subscribers would have no way to keep their reading habits private. Telegram protects that. Makes sense from the subscriber's perspective.
From the channel owner's perspective though, it means you're working with a tiny window into your own community. And that window doesn't scroll back in time.
What the limit actually costs you
Eight hundred people left the day after a particular post. Who were they? There's no way to know from the current 200-member snapshot. You see the net number went down, not who walked out or why.
Same problem with bots. An account that joined during a bot attack six months ago and quietly left is completely gone from view — but nothing stops it from returning in the next wave if you're not tracking patterns over time.
Invite link analysis hits the same wall. You ran ads on three channels, created three different links, 500 people came through link B. How many of them are still subscribed thirty days later? Without historical event data, you genuinely cannot tell — and that's the number that matters for judging whether the placement was worth it.
How TGuard builds the full picture
Instead of taking a snapshot of who's currently in the channel, TGuard records events as they happen. Every time someone joins or leaves, the Telegram Bot API sends a ChatMemberUpdated notification. TGuard catches it, timestamps it, logs the user details and the invite link they used. The history accumulates from the day the bot is connected — permanently, without resets.
TGuard only has data from the moment it's connected — no retrospective history before that. The earlier you connect it, the more complete the record.
Each event includes the user's name, username, country, last-seen status, and whether the account is flagged as a bot or premium. The invite link name shows up too, so you can see not just that someone joined via a link but which specific link brought them.
What you can actually do with this
Filter all exits within 24–48 hours after a specific post and you'll see who left — real accounts or bots, country breakdown, how long they'd been subscribed. That turns a vague "we lost 800 people" into something actionable.
Bot accounts that cycle through — join, leave, rejoin — show up clearly in the timeline. Once you spot the pattern, you can block them preemptively rather than waiting for the next attack.
For each invite link you can run a simple cohort: how many of the people who came through it are still subscribed at 30, 60, 90 days? Channel B brought 600 subscribers but 60% left inside two weeks. Channel C brought 200 and 90% stayed. That tells you everything about where to put the budget next time.
Getting started
- Add @channel_guardian_bot as an admin with Restrict Members permission.
- The bot starts recording join and leave events immediately after connection.
- Open the Analytics section in the TGuard dashboard and select Subscriber History.
- Use date and source filters to pull the view you need.
Frequently Asked Questions
Telegram limits member list visibility for privacy reasons — to avoid exposing a channel's full audience to third parties. This is an intentional design decision, not a technical constraint.
Not with Telegram's standard tools. However, bots managing the channel can accumulate a real-time history of subscriptions and unsubscriptions. This is exactly how TGuard works: from the moment it's connected, it records every join and leave event.
The full history lets you identify users who left after a specific post, detect recurring bot accounts that cycle in and out, and track the long-term retention performance of each invite link.