4 measurements spanning 7 days, net +225. 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 681โ974 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 16:17
940
+224
8 Aug 2026, 03:10
716
+1
8 Aug 2026, 02:16
715
no change
7 Aug 2026, 18:17
715
first reading
Engagement
10 posts held, back to 20 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 1 pageof Telegramโs post history, 20 posts per page.
ERR ยท 30 days
103.7%
avg views รท 940 subscribers
Avg views / post
975
9 posts measured
Reaction rate
13.2%
reactions รท views ยท ER floor
Posts in window
10
of 10 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 3 August 2026
Posts held
10 (20 July 2026 โ 3 August 2026)
Views total
8,775
Reactions total
1,162
Forwards / comments
not exposed by the public surface โ not measured, not estimated
Readings taken
8 Aug 2026, 02:16 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.
Reaction mix
1,162 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 32.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
customย 5233567011958697078
379
32.6%
customย 5418149897293542801
330
28.4%
customย 5417867215431022953
235
20.2%
customย 5415718198479698736
146
12.6%
customย 5208692721748812459
24
2.07%
๐ฅ
15
1.29%
customย 5208727940480639659
13
1.12%
customย 5208771405549674655
10
0.861%
customย 5208915922609250347
6
0.516%
๐
4
0.344%
Custom emoji. 8 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 9 of the 10 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,162reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 10 most recent posts we hold, published 20 July 2026 to 3 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.
Telegram Stars
Stars received
7
across the posts below
Posts paid on
1
of 9 we hold a reading for ยท 11%
Most on one post
7
single highest reading
A paid reaction is a reader spending Telegram Stars โ bought with money โ on a post by @Snake_s_Nest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 10 most recent posts we hold for this entry, published 20 July 2026 to 3 August 2026. Star counts above 1,000 reach us in Telegramโs short form and carry the same three-significant-figure rounding as everything else on this page.
Showing the 10 most recent of 10 posts we hold for @Snake_s_Nest. 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.
Stars beside a post are paid reactions โ Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank โ 299,778 of 1,548,671entries 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
Named by 2 registered channels โ 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.
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 14 August 2026 โ this
entry's latest reading, not the date you are reading this.
โ๐บ๐๐๐๐'๐ ๐ต๐๐๐โ (@Snake_s_Nest), 940 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Snake_s_Nest.
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.
