4 measurements spanning 15 days, net +7. 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 722–732 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Sept 2026, 07:16
730
-1
6 Sept 2026, 01:19
731
+8
28 Aug 2026, 20:45
723
no change
28 Aug 2026, 20:31
723
first reading
Engagement
7 posts held, back to 26 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.
ERR · 30 days
47.3%
avg views ÷ 730 subscribers
Avg views / post
345
7 posts measured
Reaction rate
15.1%
reactions ÷ views · ER floor
Posts in window
7
of 7 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 28 August 2026
Posts held
7 (26 August 2026 – 28 August 2026)
Views total
2,418
Reactions total
364
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
28 Aug 2026, 20:45 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.
Reaction mix
364 reactions across 7 posts, in 19 distinct kinds. The most used accounts for 23.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5458694341323136053
86
23.6%
🤣
63
17.3%
custom 5222068542693719122
55
15.1%
😁
32
8.79%
custom 5334987205750302732
22
6.04%
❤
20
5.49%
🍾
19
5.22%
custom 5188370774750147386
18
4.95%
👍
17
4.67%
custom 5208923808169222461
5
1.37%
custom 5226909726750587626
5
1.37%
👌
4
1.10%
👀
3
0.824%
💋
3
0.824%
💯
3
0.824%
🥰
3
0.824%
custom 5197274349328933892
2
0.549%
custom 5219933896702969669
2
0.549%
❤🔥
2
0.549%
Custom emoji. 8 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 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 364 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 26 August 2026 to 28 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.
🤩🤩🤩🤩🤩🤩🤩
🤩🤩🤩🤩🤩
Я даже не хочу в очередной раз говорить, насколько мне хорошо по сюжету.
Вот просто хорошо. И раскрытие героев туда же. И Райли. Всё хорошо. Но есть парочка "новинок", которые приключились со мной в актуальной обнове.
🤩🤩Призрак Лили и вся сцена на утёсе меня пробрала до мурашек.
Тут и эмоциональная составляющая, и ужас, который я прочувствовала всей душой. А у Лилии, между прочим, нет жанра "ужасы".
…
🤩🤩🤩🤩🤩🤩🤩🤩🤩
Ситуация следующая:
Сейчас запись стрима недоступна.
Но, не переживаем!
Завтра Лена очухается, придёт в себя после того, что пережила в Лилии и всё обязательно выгрузит и вк, и на бусти.
Клянусь, я пытаюсь делать всё быстрее, но пока не получается.
Но, видео по финалу Кали, вообще-то, уже доступно к просмотру
💰здесь
📺тут
💙или тут
А спонсоры уже могут начинать готовиться к стриму😏
Простите за этот пост. Но вы сами виноваты, что заплатили за интернет.
Итак. Чисто для справки: меня бесит, когда авторов обвиняют в использовании нейронок. Во-первых, потому что это хер докажешь, во-вторых, потому что в этом ебанутом сообществе любого чиха достаточно, чтобы развязалась настоящая травля. Так что такие шизотеории я не поддерживаю.
Но меня довели. Отныне я вступаю в свидетели ииговы.
Нейронки для ге…
Showing the 7 most recent of 7 posts we hold for @lenka_obsydit. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 13 September 2026 — this
entry's latest reading, not the date you are reading this.
“Ленка обсуждает👌🏻” (@lenka_obsydit), 730 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/lenka_obsydit.
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.
