Channel
@shu_stories
On this record: Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry
195subscribers
+17 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002586050418 |
|---|---|
| Type | Channel |
| Username | @shu_stories |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/shu_stories |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 10:17 | 195 | +4 |
| 9 Sept 2026, 06:16 | 191 | +2 |
| 29 Aug 2026, 23:34 | 189 | +10 |
| 16 Aug 2026, 16:13 | 179 | +1 |
| 8 Aug 2026, 13:16 | 178 | no change |
| 8 Aug 2026, 03:46 | 178 | first reading |
7 posts held, back to 27 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
46 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 52.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5460628936327194648 | 24 | 52.2% | |
| custom 5287324244269631141 | 8 | 17.4% | |
| custom 5366375672858030816 | 6 | 13.0% | |
| custom 5386465730277421816 | 5 | 10.9% | |
| custom 5323530359013406705 | 3 | 6.52% |
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 6 of the 7 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 27 July 2026 to 8 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.
хисын никогда не думал, что очередное увлечение его лучшего друга выльется в это… но вот он здесь, в нойбурге, представляется спонсором малоизвестной команды. а чонвон в полном восторге от нового члена их команды. #coulddriveyouloco #jaywon #heehoon main — jaywon; heehoon; side — beomjun; taebin; sunjake;
custom 53864657302774218162custom 54606289363271946481
🌊. . . shell we kiss? 🐚 ⠀⠀⠀⠀⠀⠀⠀⠀#yumaki ⭐️ 𝓇𝑜𝓂𝒶𝓃𝓉𝒾𝒸 𝓉𝑒𝓍𝓉 𝒶𝓊 ⠀⠀⠀🌸 #shell_we_kiss@bronzenarcisss ⠀⠀⠀. . . 🌟🌟🌟🌟 🫧 🐬🐬 На секунду показалось, что Маки предложил ввязаться в смертельную авантюру, настолько сильно подпрыгнуло сердце Юмы в груди. Это был не тот вариант отдыха, на который он рассчитывал. Но был ли этот вариант хуже? ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ 𝚋𝚛𝚎𝚊𝚔𝚒𝚗𝚐 𝚞𝚙 ➡️ 𝚖𝚎𝚎𝚝 𝚢𝚘𝚞 ➡️ shell ➡️ ⠀⠀⠀⠀⠀⠀ …
custom 53864657302774218162custom 54606289363271946481
#lemonshade Ꮗ #sunjay intertwining of destinies — SPECIAL STORY UNLOCKED ； ˢⁿˢ ᵃᵇᵒ!au — Обстоятельства вынудили Джея сделать выбор, и в спешке он оставил за спиной не только привычную жизнь, но и кое-что очень важное. Теперь это нечто находится в руках Сону. И он ищет того, кому это принадлежит... ⤷connected with heehoonki !
custom 53235303590134067051custom 54606289363271946481
々 #oneshoot w hoonki ! Пустая комната — единственное место, где два разбитых человека могли ненадолго стать опорой друг для друга. Их «ложь» о любви стала единственной правдой, которую они оба были готовы принять. буду рада фидбэку !
custom 53235303590134067052custom 53864657302774218161
🌱🌱🌱🌱
#бета_версия 93
custom 546062893632719464811custom 52873242442696311414custom 53663756728580308163
#бета_версия 92.2
custom 546062893632719464810custom 52873242442696311414custom 53663756728580308163
Showing the 7 most recent of 7 posts we hold for @shu_stories. 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.
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 2 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.
2 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“30 seconds to midnight 🍁” (@shu_stories), 195 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/shu_stories.
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.