11 measurements spanning 10 days, net -306. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 16,536–16,934 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 16:04
16,582
-43
14 Aug 2026, 02:18
16,625
-36
12 Aug 2026, 21:58
16,661
-15
11 Aug 2026, 23:55
16,676
-35
10 Aug 2026, 20:26
16,711
-55
9 Aug 2026, 23:36
16,766
-13
9 Aug 2026, 01:31
16,779
-17
8 Aug 2026, 02:06
16,796
-44
7 Aug 2026, 01:38
16,840
-48
6 Aug 2026, 02:18
16,888
no change
6 Aug 2026, 01:47
16,888
first reading
Engagement
37 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 22 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
9.28%
avg views ÷ 16,582 subscribers
Avg views / post
1,540
37 posts measured
Reaction rate
6.78%
reactions ÷ views · ER floor
Posts in window
37
of 37 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 16 August 2026
Posts held
37 (31 July 2026 – 16 August 2026)
Views total
56,909
Reactions total
3,857
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Aug 2026, 21:25 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈1,250
Videos
≈245
Links
≈555
Lifetime counters from Telegram’s own channel header, read 16 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
12s
Average length
6s
Measured directly from 2 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.
Reaction mix
3,219 reactions across 33 posts, in 8 distinct kinds. The most used accounts for 21.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5282994655242263978
690
21.4%
custom 5220092986586600921
638
19.8%
custom 5283001097693209880
489
15.2%
custom 5282952577447661524
470
14.6%
custom 5283217078713620152
354
11.0%
custom 5190705991418659942
273
8.48%
custom 5217744657382939353
177
5.50%
custom 5217438400444929936
128
3.98%
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 areTelegram’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 37 of the 37 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 3,857reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 31 July 2026 to 16 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.
Сегодня знакомимся с пополнением в команде Elian — контент-продюсером Катей! 🩵
Катя руководит креаторами бренда, ловит тренды и помогает создавать те самые видео, которые каждый день появляются у вас в ленте.
А ещё Катя живёт в Сибири и, кажется, знает каждый тренд в интернете.
🌟🌟🌟🌟🌟🌟🌟🌟
🌸Привет! Расскажи, как ты попала в контент-продакшн — и как в итоге пришла в бьюти-индустрию?
Я всегда обожала съемки, продюсиро…
Коллекция Summer Garden получилась умиротворяющей: румяна наносятся без пятен, тени растушёвываются за пару движений, бальзамы не полосят, а хайлайтер не подчёркивает текстуру.
Мы позаботились о том, чтобы ты не переживала хотя бы за макияж 🙏
Заметила, что оттенки бальзамов Solar идут не по порядку: 06, 12, 18 и 24?
Номера оттенков — это время суток, которое отражает бальзам:
🌅 06 Sunrise — нежный рассвет
🌁 12 Noon — солнечный полдень
🌌 18 Dusk — дымчатые сумерки
🌃 24 Midnight — темная полночь
Любви с первого взгляда не существует? જ⁀➴
Тогда как объяснить желание заказать всю коллекцию Summer Garden, стоит только её увидеть?
💚💚💚💚
💚💚💚Все хиты и новинки
💚💚💚уже на elianrussia.com
💚💚💚💚
💚💚💚💚💚
👇
❤️Румян много не бывает. Кажется, пора попробовать Cloud Glaze от Elian 🤍
❤️Ты готова вести за собой. Смелее, всё получится!
❤️Сегодня отличный день, чтобы напомнить близким, как сильно ты их любишь 💌
❤️Пора превращать планы на лето в любимые воспоминания 🔅
❤️Лучшее, что ты можешь выбрать сейчас, это время для себя ❤️
❤️Самое время немного замедлиться и восстановить силы ⭐
Showing the 12 most recent of 37 posts we hold for @elianrussia. 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.
Posts edited after publishing
@elianrussia edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
16 August 2026
Most recent edit
16 August 2026
Citation-graph rank
Citation-graph rank — 86,949 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 7 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@elianrussia named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@valeriyalgorevna named in 1 post, 8 August 2026 – 8 August 2026
Cite this entry
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“Elian Russia” (@elianrussia), 16,582 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/elianrussia.
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.
