Telegram RegisterThe public register of Telegram

Channel

𝐖𝐇𝐈𝐒𝐏𝐄𝐑||𝐑𝐚𝐯𝐞𝐧.

@agentwhisper

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

35subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002402137264
TypeChannel
Username@agentwhisper
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/agentwhisper

Growth

3511 Aug 2026, 12:49 — 35 subscribers12 Aug 2026, 01:03 — 35 subscribers11 Aug 2026, 12:4912 Aug 2026, 01:03
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 34–36 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 01:0335no change
11 Aug 2026, 12:4935first reading

Engagement

20 posts held, back to 13 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
62.1%
avg views ÷ 35 subscribers
Avg views / post
21.8
12 posts measured
Reaction rate
47.3%
reactions ÷ views · ER floor
Posts in window
13
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 6 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held20 (13 March 20261 August 2026)
Views total261
Reactions total62
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 12:49 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

76 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 21.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52469630020700439881621.1%
custom 52469724767678986261418.4%
custom 52467359829836769561114.5%
custom 52447443894686526541013.2%
custom 52471837290293185711013.2%
custom 524722131428812623779.21%
custom 524705972473355996156.58%
custom 524681433177709161333.95%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 9 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 76reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 March 2026 to 1 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Aug 2026, 17:36 UTC14 views10 reactionsread 11 August 2026
Photo

🌟🌟🌟 𝑺𝑬𝑪𝑶𝑵𝑫 𝑨𝑹𝑪𝑯. 𝑺.𝑯.𝑰.𝑬.𝑳.𝑫. 𝒉𝒆𝒂𝒅𝒒𝒖𝒂𝒓𝒕𝒆𝒓𝒔. 𝑨𝒏𝒅 𝒏𝒐𝒘 𝒘𝒉𝒂𝒕? Вторая арка. Штаб агентов "Щ.И.Т". А что теперь? 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟Несколько секунд никто не произносил ни слова. Я чувствовала на себе взгляды людей, которых только что отвлекла от работы. Первой опомнилась Аделин. Она резко повернулась ко мне, и по выражению её лица было понятно, что сейчас она одновременно хочет меня придушить и убедиться, что со мной всё в

custom 52470597247335599614custom 52469630020700439883custom 52471837290293185713

29 Jul 2026, 17:16 UTC18 views9 reactionsread 11 August 2026
Photo

🌟🌟🌟 𝑺𝑬𝑪𝑶𝑵𝑫 𝑨𝑹𝑪𝑯. 𝑺.𝑯.𝑰.𝑬.𝑳.𝑫. 𝒉𝒆𝒂𝒅𝒒𝒖𝒂𝒓𝒕𝒆𝒓𝒔. 𝑩𝒖𝒔𝒕𝒆𝒅. Вторая арка. Штаб агентов "Щ.И.Т". Спалили. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟Мария ещё что-то говорила, но закончить мысль не успела. Тишину кабинета разорвал короткий сигнал служебных коммуникаторов. Почти одновременно несколько устройств отозвались одинаковым сухим звуком, словно по всему штабу кто-то нажал одну кнопку. За стеклянной стеной люди, ещё секунду назад спокойно обсу

custom 52467359829836769563custom 52471837290293185713custom 52472213142881262373

25 Jul 2026, 14:00 UTC18 views9 reactionsread 11 August 2026
Photo

🌟🌟🌟 𝑺𝑬𝑪𝑶𝑵𝑫 𝑨𝑹𝑪𝑯. 𝑺.𝑯.𝑰.𝑬.𝑳.𝑫. 𝒉𝒆𝒂𝒅𝒒𝒖𝒂𝒓𝒕𝒆𝒓𝒔. 𝑷𝒍𝒂𝒏. Вторая арка. Штаб агентов "Щ.И.Т". План. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 — А должен быть какой-то особенный повод? — я медленно выдохнула и всё-таки пожала плечами. — Обычно люди не начинают искать Наташу Романофф просто из любопытства. — Почему же? — я подняла на неё взгляд. — Половина страны знает её имя. После Нью-Йорка она стала человеком, на которого многие хотели быть похожи

custom 52447443894686526543custom 52469724767678986263custom 52471837290293185713

22 Jul 2026, 16:15 UTC17 views10 reactionsread 11 August 2026
Photo

🌟🌟🌟 𝑺𝑬𝑪𝑶𝑵𝑫 𝑨𝑹𝑪𝑯. 𝑺.𝑯.𝑰.𝑬.𝑳.𝑫. 𝒉𝒆𝒂𝒅𝒒𝒖𝒂𝒓𝒕𝒆𝒓𝒔. "𝑵𝒐𝒘 𝒕𝒆𝒍𝒍 𝒎𝒆." Вторая арка. Штаб агентов "Щ.И.Т.". "А теперь расскажи мне." 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟Я догнала её уже у двери кабинета, где Аделин даже не обернулась, лишь коротко постучала костяшками пальцев по матовому стеклу и, услышав спокойное «войдите», открыла дверь. Мария Хилл сидела за длинным столом. Перед ней лежала раскрытая папка, несколько фотографий и планшет с выве

custom 52467359829836769563custom 52469630020700439883custom 52469724767678986263custom 52470597247335599611

19 Jul 2026, 16:03 UTC22 views13 reactionsread 11 August 2026
Photo

🌟🌟🌟 𝑺𝑬𝑪𝑶𝑵𝑫 𝑨𝑹𝑪𝑯. 𝑺.𝑯.𝑰.𝑬.𝑳.𝑫. 𝒉𝒆𝒂𝒅𝒒𝒖𝒂𝒓𝒕𝒆𝒓𝒔. Вторая арка. Штаб агентов «Щ.И.Т.». 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟Долго ждать не пришлось. Мы договорились с Аделин и она встретила меня у входа в здание. На ней, как всегда, не было ничего лишнего: тёмный костюм, собранные волосы и тот неподходящий для агента мягкий взгляд, который почему-то каждый раз заставлял меня чувствовать себя так, что она слишком чистая для этого места. — Я ду

custom 52469630020700439885custom 52469724767678986264custom 52472213142881262374

Showing the 12 most recent of 20 posts we hold for @agentwhisper. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 509,313 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.

“𝐖𝐇𝐈𝐒𝐏𝐄𝐑||𝐑𝐚𝐯𝐞𝐧.” (@agentwhisper), 35 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/agentwhisper.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.