Telegram shows 11.1M. The exact number is 11,143,438
Every abbreviated figure Telegram displays is a rounded string. One extra 4 KB request returns the exact integer, and both numbers ship so the rounding stays auditable.
The Telegram channel preview displays subscriber and view counts as rounded strings such as 11.1M, which is a display format rather than a measurement: 11.1M covers everything from 11,050,000 to 11,149,999. One additional 4 KB request per channel returns the exact integer — 11,143,438 in the measured case — and this Actor delivers both, as `subscribers` and `subscribers_raw`, so anyone reading the dataset can see what was rounded and by how much. View counts follow the same pattern with `views` and `views_raw`.
Key points
`11.1M` is a display string covering a range roughly 100,000 wide, so a reach report built on it inherits that uncertainty invisibly.
The exact count costs one extra 4 KB request per channel and returns a plain integer: 11,143,438 in the measured case.
Both values ship on every row — the typed number and the string as displayed — so a reader can audit the conversion rather than trust it.
View counts use the same pair, `views` and `views_raw`, and views were present on 99.2% of 893 measured posts.
Exact subscriber lookup is ignored in discover mode, because that mode opens many channels at once and the extra request per channel would dominate the run.
The channel preview shows 11.1M subscribers. That is a display format, and treating it as a measurement is how reach reports acquire an uncertainty nobody wrote down.
What the rounding hides
11.1M is three significant figures. Everything from 11,050,000 to 11,149,999 renders the same way, so the string carries a band roughly 100,000 wide. Two channels that both display 11.1M can differ by nearly a hundred thousand subscribers, and any ranking built on the displayed values cannot tell them apart.
Where the exact number comes from
Telegram serves the precise figure on a separate small page. One extra request of about 4 KB per channel returns it: 11143438 in the measured case. The Actor fetches it by default, as part of the $0.002 channel record.
Why both values ship
subscribers is the exact integer and subscribers_raw is the string Telegram displayed. A dataset that silently replaced one with the other would leave a reader no way to check the conversion, and the conversion is exactly the sort of step that goes wrong quietly — a locale that reads 1.1M as 1.1, a K that meant thousand in one row and nothing in another.
Views follow the same rule
views is the typed value and views_raw is the string as shown — 3.1M next to 3140000. Views were present on 99.2% of 893 measured posts across 9 channels, so the pair is on nearly every row.
When to turn it off
In discover mode the lookup is ignored, because that mode opens many channels at once and one extra request per channel would dominate the run. If you are reading posts rather than measuring reach, turning it off saves a request per channel and loses nothing you were going to use.
Frequently asked questions
▸How accurate is the rounded subscriber count?
`11.1M` is accurate to three significant figures, which means it covers a band about 100,000 wide. That is fine for a headline and wrong for a comparison between two channels whose displayed counts are the same.
▸What does the exact count cost?
One extra 4 KB request per channel, on top of the $0.002 channel record. It is on by default and ignored in discover mode, where opening many channels at once would make the extra request per channel the dominant cost.
▸Why keep the rounded string at all?
Because it is what Telegram published, and a dataset that silently replaces the published value with a derived one gives a reader no way to check the derivation. Shipping both is what makes the conversion auditable.
Sources
Every URL below was requested and returned a page on the date shown.
Every field the Actor returns, with the rate it was actually filled on across 893 posts in 9 channels — including the two that vary enough by channel type that an average would mislead.
A walkthrough of reading public Telegram channels anonymously: the four modes, when search beats reading a history, and what the anonymous preview does and does not render.
The Bot API cannot read a channel it is not in. MTProto needs a phone number and an api_id. The public web preview needs neither, and it is what a channel publishes to the open web.
