Telegram RegisterThe public register of Telegram
Telegram profile photo for For how long?

Channel

For how long?

@yagnom32

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

103subscribers

+5 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-1003799274770
TypeChannel
Username@yagnom32
CreatedBetween 1 February 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/yagnom32

Growth

98103100.59 August 2026 — 98 subscribers9 August 2026 — 98 subscribers16 August 2026 — 101 subscribers24 August 2026 — 103 subscribers1 September 2026 — 102 subscribers10 September 2026 — 103 subscribers9 August 202610 September 2026
6 measurements spanning 32 days, net +5. 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 97–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 16:57103+1
1 Sept 2026, 19:35102-1
24 Aug 2026, 20:34103+2
16 Aug 2026, 21:17101+3
9 Aug 2026, 22:0098no change
9 Aug 2026, 21:4798first reading

Engagement

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

What this channel posts

Video runtime
9s
Average length
9s

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.

Reaction mix

124 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 20.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 59249454511271494502520.2%
custom 54160200616661778402217.7%
custom 54248001559352042261713.7%
custom 53369027611643260991512.1%
custom 54204949107824638921512.1%
custom 54204533312040781091411.3%
custom 5337054991985170741118.87%
custom 540664779878120822354.03%

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

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

Telegram Stars

Stars received
3
across the posts below
Posts paid on
2
of 9 we hold a reading for · 22%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yagnom32. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 10 most recent posts we hold for this entry, published 8 July 2026 to 1 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Aug 2026, 20:30 UTC102 views11 reactions2 Starsread 9 August 2026

Ребятки,я пропаду на некоторое время пока проблемы не уляжутся. Если все будет плохо ак отлетит. Не теряйте,обнял❤️🤍

custom 542045333120407810910custom 54066477987812082231

29 Jul 2026, 09:09 UTC160 views10 reactionsread 9 August 2026
Photo

Минутка перекура и работаем в темпе

custom 533690276116432609910

26 Jul 2026, 14:55 UTC148 views11 reactions1 Starread 9 August 2026
Photo

Да ну нахуй 😳

custom 542049491078246389210custom 54160200616661778401

18 Jul 2026, 19:10 UTC235 views23 reactionsread 9 August 2026
Photo

Как говорил мой одногоупник "Жизнь это борьба и бейся до конца"

custom 541602006166617784013custom 53369027611643260995custom 54204533312040781094custom 54204949107824638921

17 Jul 2026, 18:00 UTC204 views13 reactionsread 9 August 2026
Photo

Живём без продыху😢

custom 59249454511271494508custom 54160200616661778405

13 Jul 2026, 19:53 UTC243 views19 reactionsread 9 August 2026
Photo

Фотосессия перед чудом😈 (Через месяц увидим другой результат)

custom 59249454511271494509custom 54248001559352042266custom 53370549919851707414

10 Jul 2026, 18:23 UTC240 views16 reactionsread 9 August 2026
Photo

Внезапный вкид👍

custom 53370549919851707417custom 54248001559352042265custom 54066477987812082234

8 Jul 2026, 20:50 UTC212 views14 reactionsread 9 August 2026
Photo

Собственно что и произошло. Телефон потерял связь с миром⚰️ Спасибо другу за поддержку и временый телефон,обнимаю родной❤️

custom 59249454511271494508custom 54204949107824638924custom 54248001559352042262

8 Jul 2026, 20:48 UTC179 views7 reactionsread 9 August 2026

Пиздец ребят.Разбил телефон со всеми данными но это ерунда,получилось кое как восстановить данные и поддерживать связь. Следующая остановка это новая мобила

custom 54248001559352042264custom 54160200616661778403

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“For how long?” (@yagnom32), 103 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/yagnom32.

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.