Telegram RegisterThe public register of Telegram
Telegram profile photo for yanchonok

Channel

yanchonok

@yanchonoook

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

182subscribers

-2 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002244343525
TypeChannel
Username@yanchonoook
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/yanchonoook

Topic

Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1821861849 August 2026 — 184 subscribers9 August 2026 — 184 subscribers23 August 2026 — 185 subscribers30 August 2026 — 186 subscribers8 September 2026 — 184 subscribers17 September 2026 — 182 subscribers9 August 202617 September 2026
6 measurements spanning 39 days, net -2. 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 181–187 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 05:38182-2
8 Sept 2026, 18:41184-2
30 Aug 2026, 09:14186+1
23 Aug 2026, 10:28185+1
9 Aug 2026, 20:31184no change
9 Aug 2026, 11:02184first reading

Engagement

14 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 14 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 56s
Average length
17s

Measured directly from 7 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

36 reactions across 11 posts, in 11 distinct kinds. The most used accounts for 19.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍719.4%
🍓616.7%
🔥616.7%
custom 5389013036725974233513.9%
😱411.1%
custom 535289429879687257725.56%
💔25.56%
custom 535980557548599396212.78%
😍12.78%
😢12.78%
🤩12.78%

Custom emoji. 3 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 11 of the 14 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 3 July 2026 to 7 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.

Recent posts

7 Aug 2026, 21:22 UTC48 views1 reactionsread 9 August 2026
Video

50х3/7 и жим с бруском 57/62/65 синглами 😇

🔥1

5 Aug 2026, 19:37 UTC115 views10 reactionsread 9 August 2026
Photo

Три недели вдали от привычной жизни оказались именно тем, что мне было нужно. Перед отъездом я провела последнюю тренировку в этом замечательном зале и приняла решение, которое для многих спортсменов покажется странным. А кто-то и вовсе скажет, что после такого я уже не спортсмен. Но я наконец честно призналась себе в том, что соревновательный пауэрлифтинг — не моя история. Ещё в самом начале своего пути я говорил…

👍7💔2😢1

30 Jul 2026, 06:32 UTC156 views1 reactionsread 9 August 2026
Video

Первоначально работали 55 синглами в 4 подхода. Все они выполнены так себе. Инерцию гасила, паузы из за этого так таковой нет. Следом небольшая проходка с бруском 57,60,62,65. Очень легенькие, едва ощутимые. 67 тоже пробовали, но мне на срыве помогли руками, поэтому не в счёт

custom 53598055754859939621

29 Jul 2026, 14:56 UTC158 views1 reactionsread 9 August 2026

Я гений. После разминки с пустым грифом хватанула первые попавшиеся блины, будучи уверенной в том, что это 10-ки. После пустого грифа, пожала 50х5 и не поняла, почему меня давят 40 🤔

🤩1

27 Jul 2026, 16:57 UTC160 viewsread 9 August 2026
Photo

Эта скамья уже начинает мне нравиться вхах

27 Jul 2026, 16:57 UTC148 viewsread 9 August 2026
Video

Поработала сегодня с тем весом, который в силах подать себе сама. Бодренькие 40х5/5 узким хватом

23 Jul 2026, 16:15 UTC175 viewsread 9 August 2026
Video

Легчайшие 50х3/6 и 52 синглами в 3 подхода.

20 Jul 2026, 17:38 UTC222 views2 reactionsread 9 August 2026
Photo

Рацион у меня отменный! х2 к силушке 💪🏻

🍓2

20 Jul 2026, 16:50 UTC188 views2 reactionsread 9 August 2026
Photo

Не смотря на то, что я приехала сюда отдыхать, продолжаю тренироваться в штатном режиме. Зал тут один, располагается в гостиничном комплексе. Цены не кусаются: разовое посещение – 300 рублей. Судя по тренерам, наградам и оборудованию, зал онли для билдеров. Тренажеров до кучи. Жимовая скамья, что мне так нужна, оставляет желать лучшего, но я не хочу придавать этому значения вхахах

custom 53890130367259742332

20 Jul 2026, 14:21 UTC166 views3 reactionsread 9 August 2026
Video

Я в двухнедельном отпуске ☺️ Приехала к бабушке погостить, в Ахтубинск. Перед отъездом потренировалась у себя на районе. Жим 52 синглами в 8 подходов.

custom 53890130367259742333

13 Jul 2026, 00:10 UTC224 views8 reactionsread 9 August 2026
Video

Как обычно, все пошло не по плану (мы его перевыполнили). Пожала 47/50х3 в 6 подходов. Это было легко, запас имеется. Спешить некуда, но там уже явно 52 вырисовываются

🍓4🔥2custom 53528942987968725772

12 Jul 2026, 17:58 UTC185 views1 reactionsread 9 August 2026
Photo

Теория бесконечного жима

😍1

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

Named by 1 registered channel — 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.

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

“yanchonok” (@yanchonoook), 182 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/yanchonoook.

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.