Music โ 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
6 measurements spanning 59 days, net +587. 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โ.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
5 Oct 2026, 22:57
606
-788
28 Sept 2026, 13:40
1,394
+211
16 Sept 2026, 02:38
1,183
-259
12 Sept 2026, 07:58
1,442
+1,423
11 Aug 2026, 16:47
19
no change
7 Aug 2026, 17:10
19
first reading
Engagement
9 posts held, back to 28 August 2025 โ the reader has not yet reached the start of this channelโs public history, so older posts may sit further back, unread. Read across 1 page 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 9 posts for this entry, the most recent from 23 September 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
126 reactions across 8 posts, in 16 distinct kinds. The most used accounts for 29.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
37
29.4%
๐ฅ
19
15.1%
๐ญ
14
11.1%
๐ฅฐ
9
7.14%
๐
6
4.76%
๐ฏ
6
4.76%
๐
6
4.76%
๐
6
4.76%
๐
5
3.97%
โคโ๐ฅ
4
3.17%
โก
3
2.38%
๐
3
2.38%
๐คฉ
3
2.38%
๐พ
2
1.59%
๐ข
2
1.59%
๐
1
0.794%
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 8 of the 9 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 126 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 9 most recent posts we hold, published 28 August 2025 to 23 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Showing the 9 most recent of 9 posts we hold for @TheHellBots. 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.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channelโs posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@TheHellBots named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
Never seen alive
References a handle that is not a live channel โ we have no record it ever was one.
@bollywoodmusicsupport1 named in 1 post, 12 August 2026 โ 12 August 2026
@ihellxyz named in 1 post, 12 August 2026 โ 12 August 2026
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 5 October 2026 โ this
entry's latest reading, not the date you are reading this.
โโโ๐๐๐ ๐๐๐๐ ๐ฝ๐๐๐โโโ (@TheHellBots), 606 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/TheHellBots.
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.
