Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
26 measurements spanning 40 days, net -153. 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 4,877–5,076 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
16 Sept 2026, 08:58
4,900
-4
15 Sept 2026, 13:20
4,904
-17
12 Sept 2026, 07:00
4,921
-1
11 Sept 2026, 19:58
4,922
-20
8 Sept 2026, 03:18
4,942
-4
6 Sept 2026, 23:17
4,946
-17
2 Sept 2026, 23:49
4,963
-1
2 Sept 2026, 13:02
4,964
-9
31 Aug 2026, 04:55
4,973
-1
30 Aug 2026, 08:05
4,974
-14
27 Aug 2026, 22:04
4,988
-1
27 Aug 2026, 04:26
4,989
-8
24 Aug 2026, 15:35
4,997
no change
24 Aug 2026, 08:36
4,997
-10
20 Aug 2026, 15:16
5,007
no change
20 Aug 2026, 12:44
5,007
-6
17 Aug 2026, 12:44
5,013
no change
17 Aug 2026, 12:14
5,013
-7
15 Aug 2026, 10:02
5,020
-8
14 Aug 2026, 11:24
5,028
first reading
Engagement
3 posts held, back to 30 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
4
66.7%
👍
2
33.3%
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 3 of the 3 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 30 April 2026 to 19 July 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.
Вуп-вуп, мазафака!
А ещё я неожиданно стал обладателем такой вот замечательной штучки - фитнес-трекера и монитора здоровья WHOOP. Это не первый мой гаджет для отслеживания активности и качества сна, но такого количества датчиков и статистики о моём "богатом внутреннем мире" я ещё не встречал! И чем дольше эта штуковина на мне калибруется, тем больше аналитики выдаёт. Жаль, что процентов 90 из этого добра я не понима…
Что ж, визуально активность Дурова по переименованию монеты TON в монету GRAM выглядит логично - трансграничные переводы должны стать удобнее (в новом формате провозить капитал через границу в заднице проще)😁
Забавно, что переименование произошло для меня как-то тихо, почти незаметно. Хотя даже бессмысленное голосование валидаторов было. Просто внезапно заметил, что в моём кошельке пропали монеты TON 🤬
На самом де…
Как-то неожиданно быстро набралось достаточное количество созданных треков для полноценного альбома😎 Из уважения к авторскому праву Марии Васильевны, на Яндекс.Музыку я его
выкладывать, разумеется, не буду, но в свой дневничок (чтобы поделиться
прекрасным с теми, кто имеет хороший вкус неравнодушен к AI-творчеству) - почему бы и нет😉
Экспериментировал и развлекался от души - перепробовал и разные голоса, и разные ин…
🔥4
Showing the 3 most recent of 3 posts we hold for @roscomnadzor_wtf. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
degenerative space @degenerativespace · 38,791 Telegram ranks this channel #17 of 76 here — alongside 75 others — read 30 August 2026
Gist Ng - Nigeria News & Gossips @Gist_Ng · 117,305 Telegram ranks this channel #40 of 42 here — alongside 41 others — read 15 August 2026
Хомяк с TON’а @homyak_s_tona · 24,481 Telegram ranks this channel #49 of 78 here — alongside 77 others — read 15 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this
entry's latest reading, not the date you are reading this.
“GRAM tap bot news” (@roscomnadzor_wtf), 4,900 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/roscomnadzor_wtf.
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.
