Channel
@elina_actrusa
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
109subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002261213198 |
|---|---|
| Type | Channel |
| Username | @elina_actrusa |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/elina_actrusa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 13:29 | 109 | -1 |
| 9 Aug 2026, 07:18 | 110 | no change |
| 7 Aug 2026, 16:19 | 110 | first reading |
5 posts held, back to 3 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 5 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
96 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 40.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5386444637693033217 | 39 | 40.6% | |
| custom 5453944678724419625 | 17 | 17.7% | |
| custom 5388644580071588913 | 11 | 11.5% | |
| custom 5357315503771634889 | 8 | 8.33% | |
| custom 5192744460206747142 | 5 | 5.21% | |
| custom 5386455796018070336 | 5 | 5.21% | |
| custom 5433855845370727300 | 5 | 5.21% | |
| custom 5453871595560904326 | 4 | 4.17% | |
| custom 5469912654166375866 | 2 | 2.08% |
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 5 of the 5 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 96 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 3 July 2026 to 27 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.
Очень понравился этот стих! Интересный смысл, о том что мы сами выбираем какой будет наш день! ❤️❤️❤️
custom 538644463769303321712custom 53886445800715889133custom 53573155037716348892custom 53864557960180703361custom 54338558453707273001custom 54538715955609043261
Посадили дерево в некрополе литераторские мостки 🌳🌳🌳
custom 538644463769303321710custom 53573155037716348892custom 54538715955609043262custom 53864557960180703361custom 54338558453707273001custom 54539446787244196251custom 54699126541663758661
Погуляли с мелким 😍
custom 53864446376930332179custom 54539446787244196254custom 53573155037716348892custom 53864557960180703361custom 54338558453707273001custom 54538715955609043261
За кого болеете? Я за Испанию
custom 545394467872441962512custom 53886445800715889138custom 51927444602067471425custom 53864446376930332171custom 54699126541663758661
Photo, posted without a caption
custom 53864446376930332177custom 53573155037716348892custom 53864557960180703362custom 54338558453707273002
Showing the 5 most recent of 5 posts we hold for @elina_actrusa. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Принцесса Элина” (@elina_actrusa), 109 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/elina_actrusa.
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.