Telegram RegisterThe public register of Telegram
Telegram profile photo for АВЭНЧИК

Channel

АВЭНЧИК

@Aw3N74

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

574subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002277808620
TypeChannel
Username@Aw3N74
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Aw3N74

Growth

57411 Aug 2026, 21:30 — 574 subscribers12 Aug 2026, 12:26 — 574 subscribers11 Aug 2026, 21:3012 Aug 2026, 12:26
2 measurements taken within a single day. 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 573–575 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:26574no change
11 Aug 2026, 21:30574first reading

Engagement

13 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
82.3%
avg views ÷ 574 subscribers
Avg views / post
473
3 posts measured
Reaction rate
1.48%
reactions ÷ views · ER floor
Posts in window
3
of 13 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 3 August 2026
Posts held13 (12 May 20263 August 2026)
Views total1,418
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 21:30 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

Video runtime
22s
Average length
6s

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

137 reactions across 11 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5442980550635701647137100.0%

Custom emoji. One 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 count beside it isTelegram’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 13 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 137reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 12 May 2026 to 3 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
15
across the posts below
Posts paid on
6
of 13 we hold a reading for · 46%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Aw3N74. 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 13 most recent posts we hold for this entry, published 12 May 2026 to 3 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

3 Aug 2026, 21:08 UTC462 views9 reactions4 Starsread 11 August 2026
Photo

the bastards🖤

custom 54429805506357016479

Signed Aw$N

3 Aug 2026, 17:23 UTC501 views4 reactionsread 11 August 2026
Photo

Loft: Euphoria party Место: ШЕЙК (ул. Советская 160А) Дата: 15.08.2026 (суббота) Время: 17:00—23:00 Возраст: 14+ ВСЕХ ЖДУ🖤

custom 54429805506357016474

Signed Aw$N

2 Aug 2026, 19:51 UTC455 views8 reactions2 Starsread 11 August 2026
Photo

🖤🖤🖤

custom 54429805506357016478

Signed Aw$N

10 Jul 2026, 19:32 UTC≈1,360 views22 reactions3 Starsread 11 August 2026
Photo

$$$

custom 544298055063570164722

Signed Aw$N

11 Jun 2026, 14:05 UTC≈2,820 views27 reactions1 Starread 11 August 2026
Photo

сегодня мент а завтра кент

custom 544298055063570164727

Signed Aw$N

10 Jun 2026, 18:06 UTC≈2,200 views21 reactions3 Starsread 11 August 2026
Photo

🔫🔫🔫

custom 544298055063570164721

Signed Aw$N

7 Jun 2026, 21:32 UTC≈1,330 views9 reactions2 Starsread 11 August 2026
Photo

🤩🤩🤩

custom 54429805506357016479

Signed Aw3N

5 Jun 2026, 17:20 UTC≈1,270 views8 reactionsread 11 August 2026
Video message

Video message, posted without a caption

custom 54429805506357016478

Signed Aw3N

4 Jun 2026, 12:29 UTC≈1,340 viewsread 11 August 2026
Photo

анонки t.me/anonaskbot?start=5bcwr

Signed Aw3N

23 May 2026, 14:09 UTC≈1,650 views10 reactionsread 11 August 2026
Video message

Video message, posted without a caption

custom 544298055063570164710

Signed Aw3N

21 May 2026, 12:39 UTC≈1,550 views13 reactionsread 11 August 2026
Photo

$$$

custom 544298055063570164713

Signed Aw3N

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

Citation-graph rank

Citation-graph rank — 927,485 of 1,480,944entries 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 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.

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

“АВЭНЧИК” (@Aw3N74), 574 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Aw3N74.

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.