Telegram RegisterThe public register of Telegram

Channel

𝚊𝚟𝚣𝚊𝚡𝚕‽

@avzaxl

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

8subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002346388494
TypeChannel
Username@avzaxl
Description|маня|14|авзаксл| вопросы? -> @maanisk лайф канал -> @mankaeyp
Created25 November 2024measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/avzaxl

Growth

87 August 2026 — 8 subscribers12 August 2026 — 8 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:178no change
7 Aug 2026, 16:098first reading

Engagement

13 posts held, back to 25 November 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 14 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Videos
8
Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
5m 21s
Average length
40s

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

228 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 35.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8135.5%
custom 51998019590574735234519.7%
custom 53462876254833384044318.9%
custom 54336641180306111114017.5%
💔198.33%

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 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 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 228reactions 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 25 November 2024 to 14 December 2024, 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

14 Dec 2024, 17:57 UTC126 views2 reactionsread 12 August 2026
Forwarded from @kavtaffeVideo

как пломбир;) 🤩#someedits ~ @kavtaffe scp -> fs_scenes буду благодарна пересылке, дабы продвинуть канал

2

Signed маня

12 Dec 2024, 19:33 UTC154 views1 reactionsread 12 August 2026

посоветуйте магазины аватарок пожалуйста 🙏🏻

1

Signed маня

11 Dec 2024, 19:13 UTC150 views31 reactionsread 12 August 2026
Video

я кринжую с озвучки, но я хочу, чтобы вы увидели😋 ❤️– #fsedit – @avzaxl

15custom 519980195905747352310custom 53462876254833384043custom 54336641180306111113

Signed маня

11 Dec 2024, 13:52 UTC148 views10 reactionsread 12 August 2026

вопрос к вам, у меня есть ролик на 3+ минуты по физике и фк, который я делала как продукт к проекту. интересно ли вам его посмотреть?)

10

Signed маня

8 Dec 2024, 15:42 UTC144 views6 reactionsread 12 August 2026
Video

Ода, пустите эту песню мне по венам😔 #edit #fs

custom 51998019590574735236

Signed маня

7 Dec 2024, 15:20 UTC157 views27 reactionsread 12 August 2026
Video

оплата у психолога прошла, и мы снова встретились♡ ❤️– #fsedit – @avzaxl

custom 5346287625483338404147custom 54336641180306111116

Signed маня

2 Dec 2024, 17:34 UTC222 views24 reactionsread 12 August 2026
Video

с кем нужно судьба сведёт снова.) sdt: @Skatingqq ❤️– #fsedit – @avzaxl

custom 5199801959057473523138custom 54336641180306111113

Signed маня

29 Nov 2024, 18:34 UTC244 views31 reactionsread 12 August 2026
Photo

я всё ещё люблю тебя..) где ты там? с кем ты там? напиши хоть слово (мне)) - ❤️– #picphoto – @avzaxl

💔195custom 53462876254833384045custom 54336641180306111112

Signed маня

28 Nov 2024, 17:56 UTC309 views27 reactionsread 12 August 2026
Video

мне несовсем нравится, но вот sdt: @twenzys ❤️– #fsedit – @avzaxl

17custom 54336641180306111116custom 51998019590574735234

Signed маня

26 Nov 2024, 12:59 UTC368 views23 reactionsread 12 August 2026
Video

такая sex sdt: @makvsks ❤️– #fsedit – @avzaxl

custom 5199801959057473523126custom 53462876254833384045

Signed маня

25 Nov 2024, 13:25 UTC327 views36 reactionsread 12 August 2026
Video

я все это видел уже;) sdt: @trusoovafan ❤️– #fsedit – @avzaxl

custom 5433664118030611111208custom 53462876254833384048

Signed маня

25 Nov 2024, 13:20 UTC208 views10 reactionsread 12 August 2026

🎞️🎞️🎞️🎞️🎞️🎞️🎞️🎞️ ❤️лс владельца: @maanisk вп/оп: да, держу 30 минут вз: не делаю в коллабах участвую 🎞️хетштеги🎞️ #fsedit #picphoto #collab #interactive -> анонимные сообщения -> голоса каналу

custom 534628762548333840482

Signed маня

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

Citation-graph rank

Citation-graph rank — 871,908 of 1,169,250entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

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

“𝚊𝚟𝚣𝚊𝚡𝚕‽” (@avzaxl), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/avzaxl.

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.