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 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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
23 measurements spanning 89 days, net -7. 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 6,433โ6,642 and does not start at zero.
Measurement log โ every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)
Subscribers
Change
4 Nov 2026, 12:26
6,526
-9
1 Nov 2026, 04:20
6,535
-5
29 Oct 2026, 06:26
6,540
-13
26 Oct 2026, 01:06
6,553
-9
23 Oct 2026, 03:17
6,562
-18
19 Oct 2026, 18:58
6,580
-4
16 Oct 2026, 20:00
6,584
-22
13 Oct 2026, 22:06
6,606
-12
8 Oct 2026, 17:42
6,618
+47
2 Oct 2026, 10:57
6,571
+101
16 Sept 2026, 20:15
6,470
+13
12 Sept 2026, 19:57
6,457
-8
8 Sept 2026, 11:41
6,465
-13
2 Sept 2026, 22:23
6,478
+14
30 Aug 2026, 18:16
6,464
+2
28 Aug 2026, 04:57
6,462
-15
25 Aug 2026, 12:23
6,477
-13
22 Aug 2026, 12:55
6,490
-8
18 Aug 2026, 18:03
6,498
-36
15 Aug 2026, 16:18
6,534
first reading
Engagement
39 posts held, back to 26 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 14 pages of Telegramโs post history, 20 posts per page.
ERR ยท 30 days
33.1%
avg views รท 6,526 subscribers
Avg views / post
2,160
7 posts measured
Reaction rate
1.25%
reactions รท views ยท ER floor
Posts in window
7
of 39 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.
What these figures were computed from
Window
Rolling 30 days ยท latest post in window 28 October 2026
Posts held
39 (26 May 2026 โ 28 October 2026)
Views total
15,123
Reactions total
189
Forwards / comments
not exposed by the public surface โ not measured, not estimated
Readings taken
6 Nov 2026, 13:22 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.
What this channel posts
Photos
58
Videos
14
Links
73
Lifetime counters from Telegramโs own channel header, read 6 November 2026 โ not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโs rounding threshold, so these counts are exact.
Video runtime
3m 41s
Average length
44s
Measured directly from 5 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
1,780 reactions across 39 posts, in 26 distinct kinds. The most used accounts for 35.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
632
35.5%
๐
184
10.3%
๐ฅ
118
6.63%
๐ฅฐ
109
6.12%
๐ฟ
94
5.28%
๐
84
4.72%
๐
62
3.48%
๐
58
3.26%
โคโ๐ฅ
56
3.15%
๐
55
3.09%
๐
44
2.47%
๐ฏ
37
2.08%
๐คฉ
35
1.97%
๐
34
1.91%
๐
33
1.85%
๐
28
1.57%
๐ณ
27
1.52%
โก
25
1.40%
๐
22
1.24%
๐ข
19
1.07%
6 further kinds
24
1.35%
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 39 of the 39 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 1,780 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 39 most recent posts we hold, published 26 May 2026 to 28 October 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
Telegramโs own โeditedโ marker: 2 of 7 posts held from the last 30 days (28.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before โ this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Showing the 12 most recent of 39 posts we hold for @ttttttuuure. 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
Named by 1 registered channel โ 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.
Named by
Channels on the register whose posts name this channel's handle.
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
1
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
1
vacant every time we have ever looked
@ttttttuuure named 1 handle 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.
@wginn_06 named in 4 posts, 8 August 2026 โ 9 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 4 November 2026 โ this
entry's latest reading, not the date you are reading this.
โ๐๐ฎ๐ฎ N O O o o o o ใ ใ . . . .โ (@ttttttuuure), 6,526 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ttttttuuure.
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.
