Channel
@GM_shalunstvoTypeBit
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003892329841 |
|---|---|
| Type | Channel |
| Username | @GM_shalunstvoTypeBit |
| Created | 20 June 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/GM_shalunstvoTypeBit |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:37 | 3 | +1 |
| 13 Aug 2026, 22:49 | 2 | no change |
| 8 Aug 2026, 07:47 | 2 | first reading |
6 posts held, back to 20 June 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 6 (20 June 2026 – 5 August 2026) |
| Views total | 50 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 22:49 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.
3 reactions across 1 post, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 2 | 66.7% | |
| 👌 | 1 | 33.3% |
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 6 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 20 June 2026 to 5 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.
⋅ ⋅ ⎯ !🔋𝗇𝗂𝗈𝗇 — 🔋𝗂𝗌𝗍 №2 — 6/30¡ 1. 𝒜𝐌𝐎𝓡 𝖨𝖭𝖥𝖮: @amorfloodlife 𝖫𝖨𝖥𝖤: @amorfloodlife 𝖴𝖲𝖤𝖱: @raifsirl [странник] 2. 𝐺Ꮧ𝐿𝐴ᑕ𝑇𝐼𝐶 ℛ𝐻𝐴𝑃𝑆Ꭷ𝐷𝑌 !¡ 空间 ೀ ˙𓂃☆ 𝖨𝖭𝖥𝖮: @GR_Inf 𝖫𝖨𝖥𝖤: @GR_lif 𝖴𝖲𝖤𝖱: @own2_gr [фаенон] 3. 𝐖𝐄𝐈𝐋ࣹᰮ𝐋ܸܿ𝐄̀𝐑֑ 𝖨𝖭𝖥𝖮: @WLLinfo 𝖫𝖨𝖥𝖤: @WLLL1FE 𝖴𝖲𝖤𝖱: @sgajje1 [блейд] 4. *ੈ‧₊˚🕸𝗜𝗠𝗠𝗢𝗥𝗧𝗔𝗟𝗜𝗧𝗬⁺˚ . 𝖨𝖭𝖥𝖮: @Immortal1ty_info 𝖫𝖨𝖥𝖤: @Immortal1ty_life 𝖴𝖲𝖤𝖱: @RapeXeX [блейд] 5. 𝑨𝗲𝘁𝗵𝗲𝗿𝗶𝘅 𝗞𝗼𝗻𝗼𝗵𝗮 𝖨𝖭𝖥𝖮: @Aetherix_inf 𝖫𝖨𝖥𝖤: @aetherix…
⋅ ⋅ ⎯ !🔋𝖺𝗆𝗂𝗅𝗒 🔋𝗇𝗂𝗈𝗇 — 1/??¡ 1. . ⸼࣪ 𓍢𓍢 ❬☾❭𝗦𝐨𝒯𝐭𝐞𝐫︩︪𝒮𝐢𝐬་༘࿐ — «Раскольников» 𝖨𝖭𝖥𝖮: @sotterlis_info 𝖫𝖨𝖥𝖤: @sotterlis_Life 𝖴𝖲𝖤𝖱: @Mini_Yuki7 [цифер]
⋅ ⋅ ⎯ !🔋𝗇𝗂𝗈𝗇 — 🔋𝗂𝗌𝗍 №1 — 29/30¡ 1. 𔓕𝇃𝇂 𝑫𝑬𝑨𝑻𝑯 ᭡ 𝑷𝑬𝑵𝑨𝑳𝑻𝒀 .ᐟ 🪼‹‹ 𝖨𝖭𝖥𝖮: @deathpenalty_1 𝖫𝖨𝖥𝖤: @deathpenalty_1life 𝖴𝖲𝖤𝖱: @rin_qp [наоми мисора] 2. 𝐒𝐇𝐀𝐑𝐃 𝐄𝐂𝐋𝐈𝐏𝐒𝐄 𝖨𝖭𝖥𝖮: @Shard_EclipseInfo 𝖫𝖨𝖥𝖤: @Shard_EclipseLife 𝖴𝖲𝖤𝖱: @Communication_PenelopeBot [химеко] 3. — 𝖬𝓮𝗿𝗂𝛂 👻 𝖨𝖭𝖥𝖮: @MeriaInfo 𝖫𝖨𝖥𝖤: @MeriaLife 𝖴𝖲𝖤𝖱: @kicksqwwx 4. ⪼ 𝓟 𝐞𝐝 𝓛 𝐢𝐠𝐡𝐭 🍓 𝖨𝖭𝖥𝖮: @red6lights 𝖫𝖨𝖥𝖤: @redlifelights 𝖴𝖲𝖤𝖱: @apple2185 [эшвейл] 5. 𝐵𝑅𝐼𝐺𝐻𝑇 𝐻𝐴𝑉𝐸𝑁 𝖨𝖭𝖥𝖮: …
💘2👌1
Sticker, posted without a caption
⋅ ⋅ ⎯ !🔋𝗇𝗂𝗈🔋𝗌 — @fihPerduletka¡ [🔋] — ᴨ0дᴄᴋᴀɜᴋᴀ! — ᴇᴄᴧи ᴋᴀᴋиᴇ-ᴛᴏ ᴄᴧ0ʙᴀ ʙᴀʍ ᴛуᴛ н3 ᴨᴏняᴛны и ʙы нᴇ ɜнᴀ3ᴛᴇ их ɜнᴀчᴇний, ᴛᴏ ᴨᴩ0чᴛиᴛᴇ ϶ᴛу ᴄᴛᴀᴛью. .. — ᴄ0юɜ ɜᴀᴋᴧючᴀеᴛᴄя ᴄ нᴀʍи ч3ᴩᴇɜ ϶ᴛᴏᴦᴏ бᴏᴛᴀ: @GMUN10N_BOT .. — ɸᴀйᴧ ᴄ уᴄᴧ0ʙияʍи ᴄᴏюɜᴀ — ᴨᴇᴩᴇйᴛи. ㅤㅤㅤㅤ[🔋]ᴄᴨ1ᴄᴋи ᴄᴏюɜ0ʙ.. .. — 1 ᴄᴨиᴄᴏᴋ. .. — 2 список. ㅤㅤㅤ [🔋]сем3йные ᴄ0юɜы.. .. — 1 список
Channel created
Showing the 6 most recent of 6 posts we hold for @GM_shalunstvoTypeBit. 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 — 672,937 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.
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.
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.
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.
“⺀𝗚𝖠𐌑𝖫𝗘 .. 𝘜𝘕𝘐𝘖𝘕 𝘋𝘖𝘙𝘐” (@GM_shalunstvoTypeBit), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/GM_shalunstvoTypeBit.
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.