Channel
@SilverbellCookie_conf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
150subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003540820762 |
|---|---|
| Type | Channel |
| Username | @SilverbellCookie_conf |
| Created | Between 1 December 2025 and 31 May 2026â estimated from Telegramâs id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/SilverbellCookie_conf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 03:09 | 150 | -2 |
| 9 Aug 2026, 09:12 | 152 | +1 |
| 8 Aug 2026, 19:46 | 151 | no change |
| 8 Aug 2026, 10:01 | 151 | first reading |
20 posts held, back to 3 August 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 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. It is computed over the 6 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (3 August 2026 â 7 August 2026) |
| Views total | 594 |
| Reactions total | 62 |
| Forwards / comments | not exposed by the public surface â not measured, not estimated |
| Readings taken | 8 Aug 2026, 19:46 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.
Measured directly from 1 video 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.
62 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 62.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5278275272162967580 | 39 | 62.9% | |
| custom 5251480749319675775 | 8 | 12.9% | |
| custom 5274054070930277810 | 8 | 12.9% | |
| custom 5275995632371281472 | 4 | 6.45% | |
| ð | 3 | 4.84% |
Custom emoji. 4 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 6 of the 20 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 62reactions in total: the kind of figure the paragraph above means by âa reaction total printed elsewhere on the pageâ.
Measured over the 20 most recent posts we hold, published 3 August 2026 to 7 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.
ð€©#ïžâ£âââð£ð¢ðŠð§ðð ð ð ð ð ð ð ð ð ð ð ð€©cr : @poisonberry1248 ð±ãœïž ð ð ð ð ð ð ð ð ð ð ⢠: @SilvyconfTAKE_bot ð€© â°â†#daily.
custom 52782752721629675804custom 52740540709302778102
Signed ÐÐÐ ÐÐÐÐÐЮ ÐÐТÐÐ @ðŒððð ð·ððð¢ð¡ ! â¡ïž #ððªððð·ðŠð³ð£ðŠððð¬ðªðŽðŽðŠð³
ð€©#ïžâ£âââð£ð¢ðŠð§ðð ð ð ð ð ð ð ð ð ð ð ð€©cr : @fuusha11 ð±ãœïž ð ð ð ð ð ð ð ð ð ð ⢠: @SilvyconfTAKE_bot ð€© â°â†#daily.
custom 52782752721629675809custom 52740540709302778102custom 52514807493196757751
Signed ÐÐÐ ÐÐÐÐÐЮ ÐÐТÐÐ @ðŒððð ð·ððð¢ð¡ ! â¡ïž #ððªððð·ðŠð³ð£ðŠððð¬ðªðŽðŽðŠð³
ð€©#ïžâ£âââð£ð¢ðŠð§ðð ð ð ð ð ð ð ð ð ð ð ð€©cr : @poisonberry1248 ð±ãœïž ð ð ð ð ð ð ð ð ð ð ⢠: @SilvyconfTAKE_bot ð€© â°â†#daily.
custom 52759956323712814724ð3custom 52740540709302778102custom 52782752721629675802
Signed ÐÐÐ ÐÐÐÐÐЮ ÐÐТÐÐ @ðŒððð ð·ððð¢ð¡ ! â¡ïž #ððªððð·ðŠð³ð£ðŠððð¬ðªðŽðŽðŠð³
ââââ>[Ð ÐÐЫÐРЫК]<ââââ âââââââââââââââââââââ ??: Psst.. Yes, you!! ð€© || ⪠âМᥲΎá§ÏÑá¥Îº в аЎЌ ËË Ö¹ ð àš â¿â¿â¿â¿â¿â¿â¿â¿â¿â¿â¿ Ë ðŒï¹ð€©ï¹â¯ Ëðá§ÑÑ Ðœá¥²á¥áŽá¥ κá§â²á¥²ÐœÐŽÑ, М᧠ΎᥱဠÊÑ á¥áŽŠÏᥲáŽÑ Ñжᥲ᥎Мá§. ð¿á§Ñᥱâ²Ñ á¥áŽŠÏá§Îºá¥ Мᥱ â²á§áŽŠÑᎠᥰá§ÐŽá¥ŽáŽÏá§á¥áŽÑá¥ŽÑ á¥°á§ÐŽ ᥎á¥áŽÑᥲÑá¥Ñ ᥠМá§Ïâ²á¥²á§ÑМ᧠Ïᥱᥲᎊá¥Ïá§ÊᥲáŽÑ... à§ ðŠ· Ö¹ Ö¹ ê°ââÖ â â â Öš ââ â â âÖ âÛ Ö¥âá©§ê± ð . â ˹ Ëž ÖŽàš Ö¹ïžµ ðá§á¥ Ïᥱκá§ÏÐŽ 38 ϶áŽá¥²Ð¶á¥±á¥.. ðá¥±ÐœÑ Ðœá¥± á¥á§áŽÑᎠᥰÑ᥎κᥲáŽÑ Мᥲ á§á§ÐœáŽŠá¥ ᥠÑᥲ᥎áŽá§ ÊÑᎊá§ÐœÑÑᎠá¥á€ âŠ
Signed ÐÐ°ÐºÐµÑ ðð
#вп
Signed ÐÐ°ÐºÐµÑ ðð
ð¥¹ð¥¹ðððð.. ððµð®ð?.. ð¡ð²ð ð ð³ð¿ð¶ð±ð®ð:: ðºð®ðŽð¶ð°ð®ð¹ ðºð²ðŒð ðºð²ðŒððŸ
Signed ÐÐ°ÐºÐµÑ ðð
ð»ð» ê° ÐÐÐÐÐ Ð ÐÐÐÐÐЫ!! ê± ð»ð»ð» ðªŠðªŠðªŠðªŠðªŠ ð»... âðŠð¢ð¥ ð¯ð¶ð³ðŽðŠ à ð© ð¶ð³ðŽðŠ ðð âðððððŠ ð»ð»ð»ð»ð ððð â ð€ÐµÐ±Ðµ ÐœÑавОÑÑÑ ÑакПй ÑОп как ... âðŠð¢ð¥ ð¯ð¶ð³ðŽðŠ à ð© ð¶ð³ðŽðŠ Оз ОгÑÑ ðððððð âðð ððð¡ððâ ð»ð»ð» ðªŠðªŠðªŠðªŠðªŠ ð» 𩺠áŽá§áŽŠÐŽá¥² áŽá¥±ÎŽá¥± áŽá§ÑМ᧠᥎ÑЎᥲ â° ð¢ð³ðµ ð€ð³ : ð¢ðšð¢ð³ð_1 ð°ð¯ ð
Signed ÐÐ°ÐºÐµÑ ðð
#вп
Signed ÐÐ°ÐºÐµÑ ðð
ââââË ðð«ð ððððâð . . ð âââð»Ð°Ñꪱ×× ×× ×× Ñðвал beautꪱ×× ×× ×× ful É×× ð³ðµ â ââââË ð«ððð it heê×× e ðð£ð ððð .
Signed ÐÐ°ÐºÐµÑ ðð
#вп
Signed ÐÐ°ÐºÐµÑ ðð
ð«ðŠð®ðµð¬ðžð¶ð® ðœðžâŠ ððððððð¡ðððð ð¡ðð¡ð ðððð¡ððð! â¹ âïŸê°à° â¥ïž à»ê± âïŸâ¹ Ñ ÐœÐ°Ñ ÑÑ ÐŒÐŸÐ¶ÐµÑÑ ÑаÑÑказаÑÑ ÐŸ ÑÐ²ÐŸÐžÑ Ð»ÑбОЌÑÑ ÑÐµÐŽÐºÐžÑ Ð¿ÐµÐ¹ÑÐžÐœÐ³Ð°Ñ , а Ñакже пПЎелОÑÑÑ Ð°ÑÑаЌО, вОЎеП, заÑОÑПвкаЌО О Ñ ÐµÐŽÐºÐ°ÐœÐŸÐœÐ°ÐŒÐž Ма ÐœÐžÑ ! Ë¡áµáµáµ зЎеÑÑ ÑÐµÐ±Ñ ÑПÑМП Ме ПÑÑÐŽÑÑ. . . áµáµáµÊ·<³
Signed ÐÐ°ÐºÐµÑ ðð
#вп
Signed ÐÐ°ÐºÐµÑ ðð
Showing the 12 most recent of 20 posts we hold for @SilverbellCookie_conf. 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 â 63,009 of 1,481,502entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 7 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.
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.
@SilverbellCookie_conf named 3 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.
References a handle that is not a live channel â we have no record it ever was one.
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 16 August 2026 â this entry's latest reading, not the date you are reading this.
âââ¯ðŠððððððððð ðððððð | : ðð + n̶o̶n̶ð ðððð.áà¹à£â (@SilverbellCookie_conf), 150 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/SilverbellCookie_conf.
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.