Telegram RegisterThe public register of Telegram

Channel

Yasenkui

@ltvnsk

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,221subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001447128920
TypeChannel
Username@ltvnsk
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/ltvnsk

Growth

1,2121,2211,216.57 August 2026 — 1,213 subscribers7 August 2026 — 1,213 subscribers7 August 2026 — 1,212 subscribers10 August 2026 — 1,218 subscribers14 August 2026 — 1,221 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +8. 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 1,211–1,222 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:451,221+3
10 Aug 2026, 09:051,218+6
7 Aug 2026, 14:311,212-1
7 Aug 2026, 05:311,213no change
7 Aug 2026, 05:261,213first reading

Engagement

12 posts held, back to 12 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
48.8%
avg views ÷ 1,221 subscribers
Avg views / post
596
1 post measured
Reaction rate
16.6%
reactions ÷ views · ER floor
Posts in window
1
of 12 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
WindowRolling 30 days · latest post in window 30 July 2026
Posts held12 (12 May 202630 July 2026)
Views total596
Reactions total99
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 05:31 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

847 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 72.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 527609515964842661061772.8%
custom 527616719483991864113215.6%
custom 5407082921917973172657.67%
custom 5408861089918125346333.90%

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 12 of the 12 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 847reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 12 May 2026 to 30 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.

Recent posts

30 Jul 2026, 11:07 UTC596 views99 reactionsread 7 August 2026
Photo

🐠 Мой отец заядлый рыболов. Как-то раз он оставил карпа дома в мокром одеяле и ушел бухать в бар вместе с друзьями. Я остался дома один и решил рассмотреть карпа получше

custom 527609515964842661081custom 527616719483991864118

15 Jul 2026, 18:01 UTC≈1,070 views31 reactionsread 7 August 2026
Photo

🏵 Главный триумф года в ру-лиге, столь долгожданное и торжественное событие. Ну, почти...

custom 527616719483991864125custom 52760951596484266106

22 Jun 2026, 10:25 UTC≈1,540 views90 reactionsread 7 August 2026
Photo

💃 Обои для супер-гаджетов. Формат 9:16 #wallpaper

custom 527609515964842661082custom 52761671948399186418

19 Jun 2026, 12:20 UTC≈1,450 views106 reactionsread 7 August 2026
Photo

🥺 Всем привет, это новая обработка

custom 527609515964842661094custom 527616719483991864112

16 Jun 2026, 13:53 UTC≈1,460 views23 reactionsread 7 August 2026
Photo

📹 Актуальное портфолио. Заказать обложку › @nibbadie

custom 527609515964842661019custom 52761671948399186414

14 Jun 2026, 07:10 UTC≈1,650 views98 reactionsread 7 August 2026
Photo

🌟 Таканаши Хошито с сомнительным напитком

custom 527609515964842661087custom 527616719483991864111

13 Jun 2026, 15:05 UTC≈1,340 views24 reactionsread 7 August 2026
Video

Покадровый эпик-гаддэм 💀

custom 527616719483991864119custom 52760951596484266105

13 Jun 2026, 14:19 UTC≈1,180 views25 reactionsread 7 August 2026
Photo

🏵 Вот так могу. Скетч › Черновик › Финал для Brok3n123

custom 527609515964842661021custom 52761671948399186414

11 Jun 2026, 13:08 UTC≈1,390 views140 reactionsread 7 August 2026
Photo

🚲 Икуё, мать ее, Кита

custom 5276095159648426610126custom 527616719483991864114

9 Jun 2026, 18:51 UTC≈1,450 views113 reactionsread 7 August 2026
Photo

🤝 Нужен уникальный ник для сети aesthetics obsession › ao.jpeg › Litvinsky › Yasenkui (Ясенку́й/Я́сень). Ээээ.... Завуалированный каламбур, но без грубости Канал по-прежнему мой. Все остается прежним, кроме названия. Не теряйтесь 😡😡😡

custom 527609515964842661096custom 527616719483991864117

17 May 2026, 14:35 UTC≈1,810 views73 reactionsread 7 August 2026
Photo

😋 Две версии непростой, мягко говоря, судьбы демасийского мужа Какая лучше: светлая или темная? Реакции соответствующие 😏

custom 540708292191797317261custom 540886108991812534612

12 May 2026, 16:14 UTC≈2,100 views25 reactionsread 7 August 2026
File

File, posted without a caption

custom 540886108991812534621custom 54070829219179731724

Showing the 12 most recent of 12 posts we hold for @ltvnsk. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Yasenkui” (@ltvnsk), 1,221 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ltvnsk.

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.