Channel
@storydes_design
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
110subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002078618312 |
|---|---|
| Type | Channel |
| Username | @storydes_design |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 9 September 2026 |
| On Telegram | t.me/storydes_design |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 23:05 | 110 | +1 |
| 9 Aug 2026, 07:31 | 109 | no change |
| 7 Aug 2026, 15:05 | 109 | first reading |
7 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 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.
81 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 25.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5431485289711289933 | 21 | 25.9% | |
| custom 5429164207780152924 | 17 | 21.0% | |
| custom 5429101548502271960 | 16 | 19.8% | |
| custom 5429200487368903066 | 12 | 14.8% | |
| custom 5465170408976172882 | 7 | 8.64% | |
| custom 5429567539568984875 | 5 | 6.17% | |
| custom 5465244857939279801 | 3 | 3.70% |
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 7 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 81 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 4 August 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.
Сегодня у меня был грустный момент. Я ехала на объект посмотрела в окно в даль, потом по сторонам, и не нашла горы. Прикиньте, я скучаю по этому чудесному Алматинскому горному горизонту. Может поэтому в проект я ставлю раковину из булыжника 😏
custom 54291015485022719606custom 54291642077801529243custom 54292004873689030662custom 54314852897112899331
Освещение решает
custom 54314852897112899336custom 54292004873689030663custom 54295675395689848752
"Что-то на красивом" ✨ - пишу я вам, а сколько за этим борьбы и потраченных нервов только знаем мы с Аней и мой муж.
custom 54291642077801529244custom 54314852897112899334custom 54292004873689030663custom 54291015485022719601
Я сегодня режим-диван, но смотрю по фоткам как ставят столешницы и примеряют раковины. Раковина вышла ну очень красивая, интересно как потом в быту, услышать отзыв
custom 54314852897112899334custom 54295675395689848753custom 54292004873689030662custom 54291015485022719601
Вы меня спрашивали , что я тут такого вкусного ем, что есть только в Мск. Вот мои любимые вкусняшки. Да весь мой заработок уходит на сладости. 🥰
custom 54291642077801529245custom 54291015485022719603custom 54314852897112899333
Примерка плиточки у нас сегодня #проект_Д
custom 54291015485022719605custom 54314852897112899333custom 54292004873689030662
Это видео описывает мое расписание в последние 2 недели
custom 54651704089761728827custom 54291642077801529245custom 54652448579392798013
Showing the 7 most recent of 7 posts we hold for @storydes_design. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Story_design” (@storydes_design), 110 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/storydes_design.
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.