#edit by zuzahelp link & xml please mark credits if u take

Channel
help fr 𝒮hýuao | alight motion
@shyyyyshy
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
221subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003719556802 |
|---|---|
| Type | Channel |
| Username | @shyyyyshy |
| 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/shyyyyshy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:28 | 221 | +1 |
| 7 Aug 2026, 03:17 | 220 | no change |
| 6 Aug 2026, 08:18 | 220 | first reading |
Engagement
12 posts held, back to 4 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 · 30 days
- 25.4%
- avg views ÷ 221 subscribers
- Avg views / post
- 56.1
- 12 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 12
- of 12 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 12 (4 August 2026 – 6 August 2026) |
| Views total | 673 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:17 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.
Recent posts
— twixtor with hae jo and cho jae mi #twixtor #mrplankton — give credits .lilixam
scenes w lee chan #любимыйсотрудник #mybiasmyboss #личан
Sticker, posted without a caption
• n-new . . . #Stickers — #Martin — bwwwwww цв st1ckerzzzz :: in comments¡? By Murphy's Arc
pr0f. ❤️ des1gń 🍴n1ckŋamê - Kellǿrd' 34 ůseŘs - @k3llor @kel4rd em0ġeŝ -🥷❤️🤩
new post with lee chan #mybiasmyboss #любимыйсотрудник #личан
Sticker, posted without a caption
– стикеры с Сон Хеном – post by @waterme1onn #стикеры #сонхен #кортис #cortis
🚨 New post by @sleepitxml #edit 🤩 link
🥹 code on #edit 🌟 🤩 @driftjiu 🤩 🤩🤩🤩🤩l1nk // my tt 🤩🤩🤩🤩xml in comments 🤩🤩🤩🤩took? « + » in comm🌟 🤩🤩🤩
[🪽] edit @meilinghelp !! ➤::link - boost #alightmotion x #edit x #xml ⤷”taken? “+” in comments!!ˎˊ˗
Showing the 12 most recent of 12 posts we hold for @shyyyyshy. 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
Republishes
Channels on the register whose posts this channel has forwarded.
@MurpCORTIS · 2,3922 posts𝗁𝖾𝗅𝗉 𝖿𝗋 𝗐𝖺𝗍𝖾𝗋𝗆𝖾𝟣𝗈𝗇 || нарезки из дорам
@waterme1onn · 2,8772 postshelp/xml & codes (alight motion)
@driftjiu · 8741 posthelp fr si
@helpfrsi · 1,8701 postlilixam
@helplilixam · 4091 post‵help fr měi | codes for am | коды для алайта от мэйлин | нарезки из дорам’
@meilinghelp · 1,6991 postpr0f. des1gń
@sadisai · 3471 postxml alight motion | sleepit
@sleepitxml · 1,4081 post𝘩𝘦𝘭𝘱 𝘰𝘧 𝘸𝘯𝘪𝘬𝘪𝘮
@wnikim · 1,2741 postzuzahelp
@zuzaheIp · 6011 post
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
Names
Channels on the register whose handles appear in this channel's posts.
@driftjiu · 8741 post‵help fr měi | codes for am | коды для алайта от мэйлин | нарезки из дорам’
@meilinghelp · 1,6991 postxml alight motion | sleepit
@sleepitxml · 1,4081 post𝗁𝖾𝗅𝗉 𝖿𝗋 𝗐𝖺𝗍𝖾𝗋𝗆𝖾𝟣𝗈𝗇 || нарезки из дорам
@waterme1onn · 2,8771 postпереходник zuzahelp
@zuzahelp · 71 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@shyyyyshy named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“help fr 𝒮hýuao | alight motion” (@shyyyyshy), 221 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/shyyyyshy.
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.