Telegram analytics and Telegram channel analytics: what each number measures, and who can see it

By Mara Vogel Published 16 October 2026 20 min read

Telegram analytics is a split subject. A channel owner gets a detailed dashboard that nobody else can see. Anyone else looking at that channel, including an advertiser or a catalogue such as TGStat, sees three numbers: subscribers, views and forwards. A bot owner gets almost nothing from Telegram and has to build the measurement into the bot. Telegram channel analytics, group analytics and bot analytics therefore answer different questions, and mixing them up is how most bad decisions about Telegram growth get made.

Every Telegram figure below comes from a Telegram page read on 16 October 2026 and named beside the figure, under the sourcing standard behind these guides. Where Telegram publishes nothing, the guide says so instead of borrowing a vendor's number. Sendhaus, an independent Telegram messaging studio, has no affiliation with Telegram Messenger Inc.

What is Telegram analytics?

Telegram analytics is the measurement of how a channel, group, bot or Mini App performs on Telegram: audience size, growth, reach per post, engagement and where new people come from. Telegram supplies native statistics only for channels and supergroups above a size line. Bots and Mini Apps rely on developer logging or an SDK, and outside tools see only the public counters of public channels.

People search for the same thing under many names. Telegram stats, tg stats and Telegram channel stats usually mean the built-in Statistics screen. Telegram channels analytics, in the plural, usually means comparing many public channels, which is what catalogue sites do. Each of those searches lands on one of the four layers in the table below, and each layer has a different owner and a different blind spot.

The scale behind those numbers is large. Telegram's ad platform says "Every month, 1 billion Telegram users generate 1 trillion views in public broadcast channels", which is why view counts, not subscriber counts, are the figure advertisers and catalogues compare.

How to check Telegram analytics for your channel

To check Telegram analytics for a channel, open the channel, tap its name to open the profile, and pick Statistics from the profile menu; on Telegram Desktop the option sits in the same menu. The screen exists only for admins allowed to view statistics, and only for channels above the size line Telegram sets. Everything on it is free, and no bot or outside login is needed.

How to check telegram analytics in practice comes down to four steps.

1. Confirm the role

   Only the owner and admins see the Statistics option, so Telegram channel analytics is private to the people running the channel. Telegram's API documentation says administrators of channels "of a certain size" can request statistics, and the client hides the button from everyone else, including subscribers.

2. Open the profile menu

   Tap the channel name at the top of the chat. On mobile, the Statistics entry is in the profile's menu; on desktop, open the channel info and use the same menu.

3. Pick a period

   Telegram's API describes period figures as "a pair of values, one at the beginning and one at the end of the period in consideration", so the headline numbers always show a change against the previous period, not a lifetime total.

4. Zoom into a graph

   Graphs that support zooming load a detailed view when you tap a day on the x-axis. Telegram's documentation calls this chart zooming and loads it through a separate request, which is why a zoomed graph can take a moment to appear.

Telegram channel analytics free of charge is the main advantage of the native screen. Nothing needs to be installed, the data comes straight from Telegram's servers, and it includes figures no outside tool can reach, such as how many subscribers muted the channel and how they found it.

Telegram channel analytics: what each number on the Statistics screen means

Telegram channel stats split into period figures, a percentage, and graphs. The period figures are followers, views per post, shares per post and reactions per post, plus the same three for stories. The percentage is the share of subscribers with notifications on. The graphs cover growth, joins and leaves, mutes, hours of activity, views and new followers by source, languages, reactions and Instant View use.

Telegram's channel tour describes the screen as graphs about "growth and the performance of its posts" and says admins can see "how many users join, leave and mute your channel, what languages they speak, how they interact with your posts, and how they found your channel – from Telegram search, by following a link, etc." The API page names each field, which is the most precise way to read the screen.

Two Telegram channel analytics fields matter more than the rest. The enabled-notifications percentage tells you how many subscribers will actually be alerted by the next post; a channel with a high follower count and a low notification share is being read by far fewer people than the headline suggests. The new-followers-by-source graph tells you which promotion worked, which is the question behind promoting a channel, group or bot by the rules and behind any paid campaign.

Why the Statistics button is missing: the 500-subscriber line

The Statistics button is missing because the channel is below Telegram's size line or the admin lacks the statistics right. Telegram's channel tour says "Advanced statistics are available for channels with more than 500 subscribers." The API documentation does not repeat the number: it calls the limit "a server-side config", returned to the app in the can_view_stats flag, so Telegram can change it.

Several blogs state a 50-subscriber line for channels. Telegram's own pages do not say 50 anywhere this guide could find, so the figure to plan around is the 500 on the channel tour, with the caveat that the server decides. A new channel therefore spends its first weeks without native Telegram channel analytics, which is exactly when owners most want to know what is working.

Below the line, Telegram channel analytics is unavailable, but the public counters still work. Each post carries a view counter, the subscriber count is visible, and a channel can tag its own links. A bot deep link carries a start parameter that Telegram's Bot Features page allows to be "up to 64 characters long", so a channel under 500 can still tell which post sent a reader to its bot. Getting over the line is a matter of growing subscribers organically; the shortcuts on offer have consequences covered in the section on reading the numbers.

One more threshold shapes what channel owners measure. Telegram's ad platform says "Ads are displayed in public channels with 1000+ subscribers", and Telegram's monetization documentation says channel owners receive 50% of the revenue from those ads. Channels that qualify get a revenue view beside their statistics, flagged in the API as can_view_revenue.

Telegram group analytics: supergroup statistics

Telegram group analytics exists for supergroups above a size line and shows members, messages, viewers and posters over the period, plus graphs of growth, joins and leaves, message volume, actions, hours, weekdays, languages and new members by source. It also lists top posters, top admins and top inviters. Telegram's API calls the size line "a server-side config" and publishes no number for groups.

The supergroup screen answers a different question from Telegram channel analytics. A channel measures reach: how many people saw a post. A group measures participation: how many people wrote, how many only read, and who brought new members in. The top-inviters list is the one figure that tells an admin whether invite links are being shared by members or by a handful of insiders, and it overlaps with what invite-member bots claim to do.

The posters-to-viewers ratio is the health figure. A group where viewers rise and posters fall is turning into a broadcast audience, and that shift often shows up beside spam: Telegram's Spam FAQ notes that "group admins can also report users who post spam in their groups", and moderation that fails drives real posters out first. How admins keep spam out is set out in spam bots and how admins stop them.

The phrase data analytics telegram group is also used by people looking for study groups about data analytics, the profession. Those are ordinary Telegram groups, and nothing about them differs from any other group; the rest of this section is about measuring a group, not joining one.

Post, story and poll statistics

Telegram channel analytics also covers single items, not only whole channels. A channel post has its own views graph and reactions-by-emoji graph, and the API can list the public channels a post was forwarded to. Stories get the same views and reactions graphs plus a list of public reposts. A poll author can see a graph of votes over time when Telegram sets the poll's can_view_stats flag.

The forwards list is the most useful of the three for growth work. Telegram's API says the method returns messages "indicating to which other public channels was a channel message forwarded", so an admin can see which public channels picked up a post. Forwards into private chats and private groups never appear there, because Telegram does not expose private chats to statistics.

Per-post data also settles timing arguments. The views-by-hours graph shows when the audience reads, and the recent-posts list shows whether a post published at a given hour beat the average. That is the evidence base for scheduling posts instead of guessing at a posting time.

Telegram analytics tools for channels you do not own: TGStat and others

Outside Telegram analytics tools read only what Telegram shows the public: subscriber counts, post view counters, forwards and mentions in other public channels. They track those numbers over time across thousands of public channels, which the native screen cannot do. They cannot see mutes, traffic sources, languages or anything about private channels, and none of them is run by Telegram.

TGStat is the best-known catalogue. TGStat telegram analytics means its public channel pages: a subscriber-growth chart, average post reach, an engagement rate, citation counts and rankings by country and category, built by indexing public channels. Brand24's 2026 roundup lists TGStat for subscriber growth tracking and channel benchmarking, beside Popsters for content performance and LiveDune for post-level reports. All of these work from the same public counters, so their numbers can differ from the native screen.

A Telegram analytics tool earns its place when you need numbers for channels you do not run: vetting a channel before buying a post, tracking competitors, or finding where a topic is discussed. For your own channel, native Telegram channel analytics is more accurate and goes deeper. Telegram analytics free tiers exist on most catalogues for basic public charts, while historical exports and monitoring tend to sit behind a subscription; prices are vendor terms, not something Telegram regulates.

Catalogue data matters most in ad buying. An agency quoting reach, or a channel quoting a price per post, is usually quoting TGStat-style public figures, and those are worth checking before reading what a Telegram ads agency sells or the published Telegram Ads prices. Telegram's own ad platform reports views and clicks for your ads, as set out in how Telegram Ads work.

Collecting member lists or messages in bulk is a different activity from reading public counters. Tools that scrape groups for usernames are covered in what Telegram scrapers do and what Telegram's terms say; an analytics tool that asks for your phone login to "see more" is in that category, not this one.

Telegram bot stats: what Telegram shows and what you log yourself

Telegram bot stats are thin on Telegram's side. A bot's public t.me page shows a monthly users count, and bots that earn from ads or Stars get revenue statistics. The Bot API has a getChatMemberCount method for chats and no method that reports a bot's own users, messages or retention. Anything beyond that has to be logged by the bot's code.

The monthly users count is public and current. On 16 October 2026, t.me/SpamBot showed 35,630,583 monthly users and t.me/BotFather showed 7,586,988. That figure matters for more than vanity: Telegram's Bots FAQ says paid broadcasts need a bot with "at least 100,000 Stars on its balance and at least 100,000 monthly active users", so a bot owner has to track the same number Telegram uses.

Every update a bot receives passes through its own server, so the bot is its own best analytics source. The table lists what a bot can record and the Telegram rule that limits each measurement.

A telegram stats bot, or telegram analytics bot, in a vendor listing usually means one of two things: a group bot such as Combot that records activity where it is an admin, or a bot that shows you a public catalogue's numbers in chat. A telegram channel analytics bot that asks to be added as a channel admin can only see what admins see in the chat itself; Telegram's statistics requests are a user method, and the API pages mark them "Only users can use this method". A bot that claims to show your channel's mute rate or traffic sources is therefore either asking for your account login or inventing the figure.

Google analytics telegram bot setups use the GA4 Measurement Protocol, which Google describes as sending events "directly to Google Analytics servers via HTTP requests". Google is explicit that the protocol is "intended to augment automatic collection" and that sending events only this way may leave "only partial reporting", so a bot-only setup should log events to its own database as well. Delivery numbers for bot broadcasts sit in the same logs, and how those sends are paced is set out in flood wait and the sending limits.

A bot that measures well is designed that way from the first commit: one event per update, a source code on every link, and a delivery record for every broadcast. That is part of our bot development and automation work, and it is the same logging that makes auto-reply options and support bots measurable.

Telegram Mini App analytics and the Telegram Analytics SDK

Telegram mini app analytics runs inside the Mini App, which is a web page, so it can use any web analytics plus the Telegram Analytics SDK. That SDK, published as @telegram-apps/analytics under the MIT licence, tracks app launches and TON Connect wallet events. Its documentation says the data is used to rank apps in the catalog. A token comes from @DataChief_bot.

The telegram mini apps analytics sdk has two set-up routes, both in its README: a script tag that loads from tganalytics.xyz, or the npm package. The README adds one rule that breaks many installs: "you must initialize the SDK before the application starts rendering." Initialization takes the token and the analytics identifier entered in @DataChief_bot. The repository describes it as a "powerful SDK and API", and the TON documentation hosts the same guide.

The Telegram Analytics SDK is narrow by design. Its disclaimer limits it to launches and TON Connect interactions, so it will not report funnels, screens or purchases. For those, telegram apps analytics means ordinary web tooling: Google Analytics through its tag, a product-analytics script, or an independent Mini App analytics service such as Telemetree, which publishes SDKs for React, JavaScript, Python, Node and Go. Whichever runs, the Mini App is still subject to Telegram's terms on user data.

Mini App and bot analytics usually end up in one place, because the same user moves between the bot chat and the app. The deep-link parameter that opened the Mini App is the join key: log it on launch and the source of every session is known. Paid traffic, referrals and channel posts can then be compared on the same basis.

How to read Telegram stats without fooling yourself

Read Telegram stats as ratios, not totals. Views per post against followers shows real reach; the enabled-notifications share shows who gets alerted; new followers by source shows what worked. A large follower count with low views and a low notification share is the usual sign of an inactive or bought audience. Telegram also calls its view counters approximate, so small differences mean little.

Telegram's Channels FAQ says view counts include "views from forwarded copies" and adds: "Please note that these numbers are approximate — we don't want to keep a record for everything you've ever viewed." A post forwarded into a large group can therefore show more views than the channel has subscribers, and a private test channel can show several views from one person.

Bought audiences show up in the ratios first. Members added by panels do not read, so views per post fall while followers rise, and the source graph shows the spike with no matching campaign. The economics and the risks are set out in bought subscribers, real versus fake and in what SMM panels sell as members and views. Telegram's API ID terms say an app used for "faking subscriber and view counters of channels" leads to being "banned forever".

Forced adds distort group figures the same way. Telegram's Channels FAQ says an owner "may invite the first 200 subscribers" and that after 200 "the channel is on its own"; the routes and errors behind adding members and its limits explain why mass adds produce members who never read. A message campaign has the same problem with its own metrics: delivered is not read, and reported is not counted.

Private-message campaigns are measured differently again. A bot broadcast gets delivery and block counts from its own logs, while a personal-account DM gets no statistics at all. The mechanics of how a direct message works on Telegram, the mutual-contacts restriction and cold DM automation explain why the second kind cannot be measured cleanly, and why accounts doing it get limited before any analytics shows a result.

Measurement is worth most when it feeds a decision. Telegram channel analytics tells a growth plan where to spend, which is the basis of our channel growth service, and delivery data tells a broadcaster when to slow down, which is part of our broadcast and bulk messaging service. The full set is on the list of Sendhaus services, and how Sendhaus works and what it declines explains why member and view packages are not on it.

Telegram analytics across messaging routes

Each Telegram messaging route leaves a different trail for analytics. A channel post has native statistics; a bot broadcast has the bot's own delivery logs; a business account reply has no statistics screen; and a personal-account message has nothing at all. Choosing a route therefore also chooses what you will be able to measure afterwards, which few route comparisons mention.

Channels are the measurable default for one-to-many messages, which is one reason they lead the four broadcast routes. A bot that sends to opted-in users is the next best, because it records every send; that is the route behind sending bulk messages through supported routes. Telegram Business features such as greeting and away messages have no Telegram analytics screen, so a connected bot has to log them.

Tools that send from signed-in personal accounts report "sent" and nothing more. That holds for most products in message sender tools sorted by what signs in, for setups built on running several Telegram accounts, and for vendors that pitch mass messaging platforms with delivery dashboards. A dashboard of that kind counts messages that left the account; Telegram publishes no read receipt for strangers and no figure for how many of those messages were reported.

The same caution applies to marketing claims built on analytics. A plan for Telegram marketing strategy and affiliate links needs source data from links and bots, not panel screenshots, and campaigns in regulated topics carry extra ad rules, as covered in what Telegram documents about crypto groups. Report counts are not analytics either: services selling mass report bots promise outcomes that no statistics screen records.

What Telegram does not publish about its statistics

Telegram publishes the fields of Telegram channel analytics and group statistics but leaves out most of the rules behind them. There is no published size line for supergroup statistics, no definition of when a view is counted, no stated error margin for "approximate" view counters, no retention or engagement benchmarks, and no public description of how the source categories are assigned. Any benchmark presented as Telegram's own is a vendor figure.

The channel threshold itself sits on two pages with two framings: a firm "more than 500 subscribers" on the channel tour and a "server-side config" in the API. This guide treats 500 as the published figure and the server as the final word. Telegram also publishes no engagement-rate formula; the "ER" figures on catalogue sites are each catalogue's own calculation, and two catalogues can report different rates for the same channel on the same day.

Telegram publishes no analytics for personal accounts, no statistics for private chats and no per-user data in any statistics view. The channel tour adds that "The subscriber list is only visible to the channel owner and admins", and nothing in the statistics API returns who viewed a post. A tool that promises to show which subscribers read a post is claiming data Telegram does not provide.

Frequently asked questions

Sources

• Telegram, Channels tour — "more than 500 subscribers", what the statistics show, subscriber list privacy.
• Telegram API, channel statistics — every field and graph, the server-side size line, message, story and poll statistics, chart zooming.
• Telegram API, stats.getBroadcastStats — "Only users can use this method", BROADCAST_REQUIRED.
• Telegram API, stats.getMegagroupStats — supergroup statistics.
• Telegram API, channel and bot ad revenue — the 50% share and revenue statistics.
• Telegram Channels FAQ — approximate view counters, forwarded views, the first 200 subscribers.
• Telegram Spam FAQ — admins reporting spam in groups.
• Telegram, Bots: an introduction for developers — "Bots can't start conversations with users."
• Telegram Bots FAQ — privacy mode, sending pace, paid broadcast thresholds.
• Telegram Bot Features — 64-character deep-link parameters.
• Telegram Bot API — getChatMemberCount; no statistics method.
• Telegram API, obtaining an API ID — the "banned forever" sentence on fake counters.
• Telegram Ad Platform — 1 billion users, 1 trillion monthly views; ads in channels with 1000+ subscribers.
• t.me/SpamBot and t.me/BotFather — public monthly users counts, read 16 October 2026.
• Telegram Analytics SDK, GitHub — scope, @DataChief_bot token, initialization before rendering, MIT licence.
• TON documentation, Telegram Analytics — the same guide on TON's site.
• Telemetree documentation — independent Mini App analytics SDKs.
• Google Analytics Measurement Protocol (GA4) — server-side events and the partial-reporting warning.
• Brand24, Telegram analytics tools (2026) — the third-party tool roundup.