Telegram RegisterThe public register of Telegram
Telegram profile photo for avilix.)

Channel

avilix.)

@avi1ix

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

26subscribers

-1 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-1002381150701
TypeChannel
Username@avi1ix
CreatedBetween 1 September 2024 and 9 January 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live6 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 6 September 2026
On Telegramt.me/avi1ix

Growth

262726.57 August 2026 — 27 subscribers11 August 2026 — 27 subscribers29 August 2026 — 26 subscribers7 August 202629 August 2026
3 measurements spanning 21 days, net -1. 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 26–27 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 01:4726-1
11 Aug 2026, 07:0227no change
7 Aug 2026, 13:5127first reading

Engagement

19 posts held, back to 9 January 2025the 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 19 posts for this entry, the most recent from 11 May 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
43s
Average length
14s

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

9 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5255912455489468512444.4%
custom 5257977943916821153333.3%
custom 5326057225712579350222.2%

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

Measured over the 19 most recent posts we hold, published 9 January 2025 to 11 May 2025, 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

11 May 2025, 14:08 UTC74 viewsread 11 August 2026

епт.. откуда тут вообще подписчики взялись.. 😔

14 Apr 2025, 16:20 UTC87 viewsread 11 August 2026

То самое чувство, когда вы покупаете человеку книгу, о которой он давно мечтал, и букет цветов, чтобы сделать приятно, а он пропадает из сети и не выходит на связь.

15 Feb 2025, 19:59 UTC192 viewsread 11 August 2026

чёт я забросила блог... рест не пошёл мне на пользу 🔞🔞

31 Jan 2025, 16:16 UTC218 views3 reactionsread 11 August 2026
Photo

вот такую девушку мне надо. дайте пж у кого есть 👄👄👄

custom 52559124554894685121custom 52579779439168211531custom 53260572257125793501

12 Jan 2025, 09:47 UTC205 views1 reactionsread 11 August 2026
Video

мне скучно... я вспоминаю детство 📦

custom 52559124554894685121

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

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

“avilix.)” (@avi1ix), 26 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/avi1ix.

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.