Channel
@sugar3dscf
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
211subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003885950490 |
|---|---|
| Type | Channel |
| Username | @sugar3dscf |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/sugar3dscf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 07:07 | 211 | +13 |
| 7 Aug 2026, 04:32 | 198 | no change |
| 7 Aug 2026, 02:30 | 198 | first reading |
20 posts held, back to 6 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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 6 August 2026) |
| Views total | 305 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04:32 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.
5 reactions across 1 post, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 3 | 60.0% | |
| custom 5366337675282390806 | 1 | 20.0% | |
| custom 5368389703282238964 | 1 | 20.0% |
Custom emoji. 2 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 1 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 5reactions 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 6 August 2026 to 6 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.
🤩🌟 ℋɛʟʟ૦, ᴡᴇʟᴄᴏᴍᴇ ᴛᴏＯ . . 🪽 🤩🎁 🥹t.me.TheobaldthebirdCF🤩🎁 Почему по Theobaldthebird так мало кф ? ?🌟 Who is the biggest bird ? ?🌟🌟 🌟Здесь ты можешь обсудить и узнать больше того что связано с ним ! 🤩 🌟🌟Theo on 🥹 YouTube Twitter Tiktok 🥹Mp post 🥹 take bot🥹 boost cr: Camijo_022 on 𝕏
Signed ㅤㅤ𝆹۪⃨𝆬݃⃜ ⃪ʍؘ͜𝗲̸ᩧ𝐨ᷓɯ̸ؙ᳟𝐞ч⃪ᰰᴋؒ𝗮̸.⵿𑪍𐇽𖹭֮ᵗ᷒ᰰㅤㅤ
🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟🌟 🥹. 🌟🌟🌟🌟🌟🌟🌟🌟 .🪦🪦🪦 а то есть дейли по таким майнкрафтерам, как orionnova32 и div_y, участвующих вместе в unserious smp. присоединяйтесь к нам, чтобы делиться контентом по этому дуо или наслаждаться им! 🌟🌟🌟🌟🌟🌟 💤🎀🎀🎀🎀🌩🌩🌩🌩🌩🌩 ⭐🔵😀 🌟🌟🌟🌟🌟 .. . 🤩🤩🤩 * unserious smp - это сюжетный смп сервер , созданный примерно недавно, 8 января, так что это ваш шанс успеть подшарить за него и стать олдом 🎀🎀🎀✨😀😀 [ navi
Signed ㅤㅤ𝆹۪⃨𝆬݃⃜ ⃪ʍؘ͜𝗲̸ᩧ𝐨ᷓɯ̸ؙ᳟𝐞ч⃪ᰰᴋؒ𝗮̸.⵿𑪍𐇽𖹭֮ᵗ᷒ᰰㅤㅤ
. ٬𝓖⑅ᚑ ᱤюбишь крꪮликов и 𝐦⵿۫۫айншилд? 𝅄 Тогда теб𝐞ۣۢ 𝐤۫۫ нам! ᧁ𝆬ꪮбро пожаловать в.... 𝕜рольᤐилд!
Signed ㅤэнвилушкаㅤ
Мы НЕ принимаем тейки про флуд! ꐚ ꒰ В анстейбл фд любят... 𝑡 ִ 𝑚𝑒 ︶︶ 𝓌. ᧓ ʾ۫ׄ ࣯
Signed ㅤэнвилушкаㅤ
Pωᑯᥙ⳽ᖾᥱᥒƙᥙ 𔓕 ᥴꪮꪀᠻꫀડડⅈꪮꪀ - ' П✻︩𝆬 дуᤐֹꫀнькບ࣪ ບ࣪ 𝙣꯭ִ𝆬уг✻︩𝆬ду ɬׁ𐓟к ᨻׁ︩𐓟л✻︩𝆬 к✻︩𝆬нɬׁꫀнɬׁ𐓟 ' - ' Мнꫀ нթִּ𐓟вບ࣪ɬׁɕִׄя вз𐓟ບ࣪ᨻׁ︩✻︩𝆬дꫀйɕִׄɬׁвບ࣪ꫀ дуᤐֹкບ࣪ ບ࣪ 𝙣꯭ִ𝆬уг✻︩𝆬д𐓟 ' - ' Х✻︩𝆬чу 𝙣꯭ִ𝆬✻︩𝆬к𐓟з𐓟ɬׁь 𐓟թִּɬׁ 𝙣꯭ִ𝆬✻︩𝆬 𝙣꯭ִ𝆬вдуᤐֹк𐓟ᨻׁ︩ ' Т✻︩𝆬гд𐓟 ɬׁꫀᨢꫀ к н𐓟ᨻׁ︩ в кф! Н𑜅ִϐִυִટ꯭𑜅ִцυִяִׄ
Signed ㅤэнвилушкаㅤ
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 😀🐏🐏🤩💕𝗲𝗹𝗰𝗼𝗺𝗲 𝘁𝗼 𝘁𝗵𝗲. . . 🎀𝗲𝗶𝗻 𝗦𝗠𝗣😀🤩🤩🤩 😀 Бледный сад, место которое вызывает страх из-за звучания скрипа деревьев и из-за него появляется ощущение, что за Вами следят, но самое страшное не это, а то что ни один живой организм не смог выжить в нём, ведь чем больше он распространялся, тем меньше мобов становилось в мире и ни одно растение не способно остановить это бедствие. Сможете ли Вы узнать причину, по…
Signed ㅤэнвилушкаㅤ
⏜݄͡ . 𝙬𝙚𝙡𝙘𝙤𝙢𝙚 𝙩𝙤 𝙇𝙖𝙯𝙪𝙡𝙞 𝙈𝙞𝙣𝙚𝙘𝙧𝙖𝙛𝙩 𝙁𝙡𝙤𝙤𝙙¡! ౿౿ .наш флуд был создан с целью найти хорошее общение, времяпровождение и друзей!𓈒 . 𓂃 🫂 ౿౿ .флуд так же нацелен на дружескую атмосферу на майнкрафт сервере с небольшим лором.𓈒 . 𓂃 🧿 ⏜݄͡ заинтересовало? тогда посмотри инфо и вступай¡! 🌀 ౿౿ .бот для вступления: @lazul1bot 𓈒 . ੭ 𓂃 ゛. .
Signed ㅤэнвилушкаㅤ
Posted without readable text
Signed ㅤэнвилушкаㅤ
ㅤ🔹𝖾𝖺𝗋𝖼𝗁 𝗌𝗍𝗂𝖼𝗄𝖾𝗋𝗌 𝖿𝗋𝗈𝗆 𝗆𝖼𝗒𝗍 𝖺𝗇𝖽 𝖱𝗈𝖻𝗅𝗈𝗑? 🌫🌫🌫 𝖧𝖾𝗋𝖾 𝗒𝗈𝗎 𝖼𝖺𝗇 𝖿𝗂𝗇𝖽 𝖾𝗏𝖾𝗋𝗒𝗍𝗁𝗂𝗇𝗀 𝗒𝗈𝗎 𝗇𝖾𝖾𝖽. 🌫🌫 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ㅤㅤ𝖬𝗎𝗍𝗎𝖺𝗅 𝗉𝗂𝖺𝗋ㅤ⋮☁️⋮ㅤ 𝗉𝗋𝗂𝖼𝖾 🤩 𝖻𝗈𝗍
Signed ㅤэнвилушкаㅤ
🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩🤩🤩 ассоциации യ 🐈⬛ ₊ Ассоциируешь персонажей uu smp с кем-либо/чем либо? Поделись здесь! 🎀 😀😀 🎀 🤩 ° ꒱ ꒱ 🔡
Signed ㅤэнвилушкаㅤ
ㅤ♯ 🤩 да, я кинню SpokeIsHere, и даже самые близкие люди не знают меня на все 100% Да, я кинню и... | @MCYTkinnbot
Signed ㅤэнвилушкаㅤ
😛🤨🤣Х 🥸😆😌 😄😘🥰🥹😆😋😋🤣😘🥰 🔚 😁😀🤣😌🤩🌟 🔤щете побольше контент про Твиксель?𔓕 ゙⃞ִ 😀😀😀 🔤 может вы его кинн?ֺ ܻ🌟 🔤ли может быть хотите показать арт/видео про нему??˓𓄹 ࣪˖🌟 ᅠᅠᅠᅠᅠТоварищ! ᅠᅠᅠТы по адресу блять. 😀😀😀😀 ᅠᅠᅠ😆обро Пожаловать! ᅠᅠᅠᅠᅠᅠᅠ😀😀😀😀 Навигация😄
Signed ㅤэнвилушкаㅤ
Showing the 12 most recent of 20 posts we hold for @sugar3dscf. 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 — 60,018 of 1,189,255entries 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 18 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.
@sugar3dscf 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“ִ۫ ₍ ₍ 𝗌𝗎𝗀𝖺𝗋𝟥𝖽𝗌 𝖽𝖺𝗂𝗅𝗒&&𝖼𝖿 ! ֺܹ✿॒̥࣪” (@sugar3dscf), 211 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sugar3dscf.
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.