These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views per post sit far above this size band
5,290 average views per post against 5,597 subscribers β an engagement rate of 94.5%. Across the 83,935 registered channels in the same cohort β 3,163β9,999 subscribers β the middle half sit between 5.30% and 21.9%, with a median of 11.3%.
What this was computed from
Window
30 days (26 July 2026 β 25 August 2026)
Posts measured
18 of 18 published in the window (0 exact, 18 rounded by Telegram)
Views totalled
95,160
Mature posts only
94.5% over 18 posts read at least 24h after publication
Β±0.053% of the figure, from Telegramβs rounding
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3Γ away from that cohortβs median β above it β on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes β audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channelβs own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 25 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through β we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
6 measurements spanning 14 days, net +679. 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,814β5,699 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 21:04
5,597
+167
19 Aug 2026, 06:23
5,430
+71
16 Aug 2026, 02:05
5,359
+118
12 Aug 2026, 11:15
5,241
+325
9 Aug 2026, 01:40
4,916
-2
8 Aug 2026, 11:18
4,918
first reading
Engagement
22 posts held, back to 24 July 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 4 pagesof Telegramβs post history, 20 posts per page.
ERR Β· 30 days
94.5%
avg views Γ· 5,597 subscribers
Avg views / post
5,290
18 posts measured
Reaction rate
0.663%
reactions Γ· views Β· ER floor
Posts in window
18
of 22 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 10 August 2026
Posts held
22 (24 July 2026 β 10 August 2026)
Views total
95,160
Reactions total
631
Forwards / comments
not exposed by the public surface β not measured, not estimated
Readings taken
12 Aug 2026, 05:06 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
Video runtime
7m 10s
Average length
1m 12s
Measured directly from 6 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
882 reactions across 22 posts, in 19 distinct kinds. The most used accounts for 64.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
β€
566
64.2%
π€¬
70
7.94%
π
45
5.10%
π₯°
41
4.65%
customΒ 6113924871144605986
39
4.42%
π
34
3.85%
π€―
19
2.15%
π
10
1.13%
π
9
1.02%
π
8
0.907%
π₯
8
0.907%
π±
8
0.907%
π€
8
0.907%
π’
6
0.68%
customΒ 5199885118214255386
3
0.34%
customΒ 5422446685655676792
3
0.34%
π
3
0.34%
π
1
0.113%
π€£
1
0.113%
Custom emoji. 3 of the rows above are 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 22 of the 22 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 882reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 22 most recent posts we hold, published 24 July 2026 to 10 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.
Showing the 12 most recent of 22 posts we hold for @OneGarenaMod. 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 β 172,398 of 1,603,376entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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
@OneGarenaMod 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.
@proxyfileupdate named in 2 posts, 9 August 2026 β 13 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 22 August 2026 β this
entry's latest reading, not the date you are reading this.
ββΆππ | ππππππ πππ πππβ (@OneGarenaMod), 5,597 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/OneGarenaMod.
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.
