Gaming โ 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 the other topics.
Growth
56 measurements spanning 88 days, net -1,296. 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 11,389โ13,073 and does not start at zero.
Measurement log โ every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)
Subscribers
Change
3 Nov 2026, 11:04
11,583
-16
2 Nov 2026, 11:31
11,599
-10
1 Nov 2026, 09:16
11,609
-20
31 Oct 2026, 11:34
11,629
-26
30 Oct 2026, 07:56
11,655
-10
29 Oct 2026, 05:38
11,665
-12
28 Oct 2026, 02:11
11,677
-19
27 Oct 2026, 00:19
11,696
-7
26 Oct 2026, 03:28
11,703
-12
25 Oct 2026, 00:46
11,715
-10
24 Oct 2026, 04:08
11,725
-15
23 Oct 2026, 04:16
11,740
-12
22 Oct 2026, 02:00
11,752
-16
20 Oct 2026, 22:54
11,768
-9
19 Oct 2026, 18:47
11,777
-13
18 Oct 2026, 19:57
11,790
-18
17 Oct 2026, 20:58
11,808
-7
16 Oct 2026, 22:14
11,815
-23
15 Oct 2026, 19:18
11,838
-6
14 Oct 2026, 18:46
11,844
first reading
Engagement
29 posts held, back to 12 May 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 49 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 29 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 59s
Average length
1m 00s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel โ not this channelโs whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegramโs own rounded chrome, so it carries no โ mark.
Reaction mix
51 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 82.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
42
82.4%
๐ฅ
5
9.80%
๐
2
3.92%
๐ค
1
1.96%
๐ฅฐ
1
1.96%
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 17 of the 29 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 51 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 29 most recent posts we hold, published 12 May 2026 to 3 September 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.
Showing the 12 most recent of 29 posts we hold for @Sarifgamingofficial. 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.
Posts recorded as deleted after publishing
We recorded 3 posts on @Sarifgamingofficial as deleted โ posts this register held that were missing from the channelโs public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channelโs public page, and when โ not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
11 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
1
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 3 November 2026 โ this
entry's latest reading, not the date you are reading this.
โ๐ฆ๐๐ฅ๐๐ ๐๐๐ ๐๐ก๐ ๐ข๐๐๐๐๐๐๐โ (@Sarifgamingofficial), 11,583 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Sarifgamingofficial.
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.