Пока ходил фоткать наступил на ежа, я очень испугался, он видимо тоже
❤4custom 52063337582061355383🤮1🥰1

Channel
@rosese
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
200subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001208861545 |
|---|---|
| Type | Channel |
| Username | @rosese |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/rosese |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 08:57 | 200 | -1 |
| 20 Aug 2026, 22:52 | 201 | +2 |
| 13 Aug 2026, 06:54 | 199 | -1 |
| 7 Aug 2026, 04:32 | 200 | no change |
| 7 Aug 2026, 04:04 | 200 | first reading |
15 posts held, back to 31 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 15 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
119 reactions across 15 posts, in 23 distinct kinds. The most used accounts for 35.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 42 | 35.3% | |
| custom 5206333758206135538 | 16 | 13.4% | |
| 👏 | 6 | 5.04% | |
| 😍 | 6 | 5.04% | |
| 🤮 | 6 | 5.04% | |
| custom 5222390991658432217 | 4 | 3.36% | |
| 🍓 | 4 | 3.36% | |
| custom 5226483640225004925 | 3 | 2.52% | |
| custom 5246855365894621721 | 3 | 2.52% | |
| custom 5416099467021536210 | 3 | 2.52% | |
| ❤🔥 | 3 | 2.52% | |
| 🐳 | 3 | 2.52% | |
| 💔 | 3 | 2.52% | |
| 🙏 | 3 | 2.52% | |
| 🥰 | 3 | 2.52% | |
| custom 5226885992761295084 | 2 | 1.68% | |
| ✍ | 2 | 1.68% | |
| 🤔 | 2 | 1.68% | |
| ⚡ | 1 | 0.84% | |
| 🌚 | 1 | 0.84% | |
| 3 further kinds | 3 | 2.52% |
Custom emoji. 6 of the rows above are 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 15 of the 15 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 119 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 31 July 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.
Пока ходил фоткать наступил на ежа, я очень испугался, он видимо тоже
❤4custom 52063337582061355383🤮1🥰1
Нам провели свет в будку!! Теперь птичьи домики горят и охлаждаются внутри кондером 😁
custom 52264836402250049253custom 52063337582061355382⚡1❤🔥1🤮1
Моя первая анимация "Единственный грибной слизняк поэт"
👏6❤2🥰2🤮1custom 52063337582061355381
Прост
😍4❤1💋1custom 52063337582061355381custom 52468553658946217211
Спокойной ночи 🛏️
❤5😍2custom 52063337582061355382
Вот музицировал(не мешал)
❤6🙏3🤔1🤮1
Депутат Увильдов
❤3🐳3🤮1custom 52468553658946217211
МЫ
custom 52223909916584322174custom 52268859927612950842❤1🤮1custom 52063337582061355381
Послушал за утро 39 раз Я выл я выл я выл Каждая строчка золотом Страшно, но не настолько чтобы остаться живым
custom 52063337582061355382❤1💔1custom 52468553658946217211
Я хотел позор и получал респект
custom 52063337582061355383🤔1custom 54160994670215362101
Будущего нет, твин пикс скачать последний сезон
❤4✍1❤🔥1
Я был я был я был
❤5custom 54160994670215362102❤🔥1🌚1
Showing the 12 most recent of 15 posts we hold for @rosese. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Колокол безденежных единиц” (@rosese), 200 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/rosese.
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.