🤩🤩🤩🤩🤩 @rusyaOBB 🐈
🥰7custom 52422164876823467893custom 53953579575526095183
Signed Ольга. Руся.

Channel
@rusyaBB
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
157subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002355462355 |
|---|---|
| Type | Channel |
| Username | @rusyaBB |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 6 September 2026 |
| On Telegram | t.me/rusyaBB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 01:32 | 157 | +1 |
| 21 Aug 2026, 18:56 | 156 | +3 |
| 8 Aug 2026, 19:15 | 153 | no change |
| 7 Aug 2026, 16:11 | 153 | first reading |
19 posts held, back to 14 April 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 19 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 18 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
205 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 31.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 64 | 31.2% | |
| custom 5242216487682346789 | 32 | 15.6% | |
| custom 5395357957552609518 | 25 | 12.2% | |
| custom 5364201435858744869 | 23 | 11.2% | |
| custom 5244910664832532110 | 21 | 10.2% | |
| 😍 | 18 | 8.78% | |
| 🥰 | 14 | 6.83% | |
| custom 5391054323012608736 | 8 | 3.90% |
Custom emoji. 5 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 19 of the 19 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 205 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 14 April 2026 to 2 July 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.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
🥰7custom 52422164876823467893custom 53953579575526095183
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
😍5custom 53642014358587448694custom 52422164876823467893
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
custom 52449106648325321105custom 53953579575526095184custom 53910543230126087363
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤5custom 52422164876823467894custom 53953579575526095184
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤6custom 52422164876823467894custom 53953579575526095184
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤5custom 52449106648325321104custom 53953579575526095184
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
custom 53642014358587448695custom 52449106648325321104❤3
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤4custom 52422164876823467894🥰3
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
custom 53642014358587448694custom 52422164876823467893❤2
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤5😍4custom 52449106648325321103
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
custom 53642014358587448695custom 53910543230126087364❤3
Signed Ольга. Руся.
🤩🤩🤩🤩🤩 @rusyaOBB 🐈
❤4😍4custom 52422164876823467894
Signed Ольга. Руся.
Showing the 12 most recent of 19 posts we hold for @rusyaBB. 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Руся Бусы🍀” (@rusyaBB), 157 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/rusyaBB.
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.