Sticker, posted without a caption

Channel
ꨴ υׁׅ݊ꪀⅈ’𝓼 ժׁׁׅׅ݊ᨵׁׅׅrꩇׁׅ֪݊ .ᐟ
@unisdorm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
53subscribers
+0 since we began measuring on 18 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003553613843 |
|---|---|
| Type | Channel |
| Username | @unisdorm |
| Description | qυׁׅꫀ :: @udquebot ╰┈➤ ꩇׁׅ֪݊ы ни в кᨵׁׅׅем слᨮׁׅ֮чаꫀׁׅܻ݊ не пропɑׁׅгандυׁׅруем насυׁׅлие,упᨵׁׅׅтреблꫀׁׅܻ݊ние & прᨵׁׅׅчее-прочꫀׁׅܻ݊е . . . |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/unisdorm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:22 | 53 | no change |
| 18 Sept 2026, 14:47 | 53 | first reading |
Engagement
20 posts held, back to 7 September 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 59.5%
- avg views ÷ 53 subscribers
- Avg views / post
- 31.6
- 20 posts measured
- Reaction rate
- 15.7%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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. It is computed over the 10 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 20 (7 September 2026 – 18 September 2026) |
| Views total | 631 |
| Reactions total | 50 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Sept 2026, 15:22 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
- Photos
- 7
- Links
- 138
Lifetime counters from Telegram’s own channel header, read 18 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
50 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 24.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5314598102643011613 | 12 | 24.0% | |
| custom 5316577665954640488 | 8 | 16.0% | |
| custom 5314282744669303795 | 7 | 14.0% | |
| custom 5422681942489332796 | 6 | 12.0% | |
| custom 5314708028035984595 | 5 | 10.0% | |
| custom 5368664765872763159 | 4 | 8.00% | |
| custom 5314395869812912039 | 2 | 4.00% | |
| custom 5323453805516320507 | 2 | 4.00% | |
| custom 5314786488498547248 | 1 | 2.00% | |
| custom 5316941067432529387 | 1 | 2.00% | |
| custom 5366161010392593560 | 1 | 2.00% | |
| custom 5384369627323177947 | 1 | 2.00% |
Custom emoji. Every row above is a 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 are Telegram’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 10 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 50 reactions 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 7 September 2026 to 18 September 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.
Recent posts
к𐐼жется , у 🎁 🤩 к𑄜г𑄜 ➖ т𑄜 из 𑄜бщ𐐼ги п𑄜явился с𑄜бств🔡н𐓣ый бл𑄜г . . . 🌟 @ ким джэхи 🌟 ✨ д𑄜бр𑄜 п𑄜жал𑄜вать в Юнсыль !
custom 53142827446693037951custom 53143958698129120391custom 53145981026430116131custom 53147080280359845951custom 53147864884985472481custom 53661610103925935601
Sticker, posted without a caption
упс ! 🎁 🤩 кт𑄜 ➖ т𑄜 , к𐐼жется , приб𑄜лел . . . ✨ джу сокген берет б𑄜льничный д𑄜 1 октября ! ждем тв𑄜ег𑄜 в𑄜звращения .
custom 53142827446693037951custom 53145981026430116131custom 53147080280359845951
Sticker, posted without a caption
упс ! 🎁 🤩 кт𑄜 ➖ т𑄜 , к𐐼жется , приб𑄜лел . . . ✨ пак сэми берет б𑄜льничный д𑄜 1 октября ! ждем тв𑄜ег𑄜 в𑄜звращения .
custom 53142827446693037951custom 53145981026430116131
Sticker, posted without a caption
упс ! 🎁 🤩 кт𑄜 ➖ т𑄜 , к𐐼жется , приб𑄜лел . . . ✨ икено берет б𑄜льничный д𑄜 30 сентября ! ждем тв𑄜ег𑄜 в𑄜звращения .
custom 53142827446693037951custom 53143958698129120391custom 53145981026430116131
Sticker, posted without a caption
упс ! 🎁 🤩 кт𑄜 ➖ т𑄜 , к𐐼жется , приб𑄜лел . . . ✨ гым сонджэ берет б𑄜льничный д𑄜 30 сентября ! ждем тв𑄜ег𑄜 в𑄜звращения .
custom 53142827446693037951custom 53145981026430116131custom 53147080280359845951
Sticker, posted without a caption
✨с в𑄜звр𐐼щением ! 🎁 🤩 нобуаки хида г𑄜т𑄜в вн𑄜вь п𑄜сещ𐐼ть з𐐼нятия в « Кёнмён » . 🌟➖➖О5.О9 ➖ 12.О9➖➖➖
custom 53142827446693037951custom 53145981026430116131custom 53147080280359845951
Showing the 12 most recent of 20 posts we hold for @unisdorm. 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.
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 3 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ꨴ υׁׅ݊ꪀⅈ’𝓼 ժׁׁׅׅ݊ᨵׁׅׅrꩇׁׅ֪݊ .ᐟ” (@unisdorm), 53 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/unisdorm.
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.