Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙰𝚈𝙾

Channel

𝙰𝚈𝙾

@Ayooty20

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

22,054subscribers

+5,033 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002283233872
TypeChannel
Username@Ayooty20
Description‏مِش كُل الناسْ هَتكون صافيَه زَيك . لطلب التمويل @Ayootii20 @Ayoo18o229BOT
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/Ayooty20

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

15,400 average views per post against 22,054 subscribers — an engagement rate of 69.7%. Across the 2,233 registered channels in the same cohort — 10,003–31,605 subscribers, posting mainly in Arabic — the middle half sit between 2.12% and 10.3%, with a median of 5.07%.

What this was computed from
Window30 days (30 August 2026 – 29 September 2026)
Posts measured13 of 13 published in the window (2 exact, 11 rounded by Telegram)
Views totalled199,744
Mature posts only89.4% over 10 posts read at least 24h after publication
Subscribers22,054 measured 25 September 2026
Cohortb10000:ara · 2,233 channels · p10 0.727% · p25 2.12% · p50 5.07% · p75 10.3% · p90 19.1%
Position in cohort99.597th percentile · 13.7× the cohort median
Uncertainty±0.043% of the figure, from Telegram’s rounding
Post languageArabic · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 29 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

17,02122,05419,537.57 August 2026 — 17,021 subscribers7 August 2026 — 17,021 subscribers8 August 2026 — 17,143 subscribers9 August 2026 — 17,256 subscribers10 August 2026 — 17,236 subscribers11 August 2026 — 17,255 subscribers12 August 2026 — 17,203 subscribers13 August 2026 — 17,198 subscribers14 August 2026 — 17,244 subscribers16 August 2026 — 17,265 subscribers17 August 2026 — 17,486 subscribers18 August 2026 — 17,451 subscribers19 August 2026 — 17,614 subscribers20 August 2026 — 17,813 subscribers22 August 2026 — 18,001 subscribers23 August 2026 — 18,095 subscribers25 August 2026 — 18,072 subscribers25 August 2026 — 18,089 subscribers27 August 2026 — 18,275 subscribers28 August 2026 — 18,452 subscribers29 August 2026 — 18,560 subscribers30 August 2026 — 18,748 subscribers31 August 2026 — 18,892 subscribers1 September 2026 — 19,059 subscribers2 September 2026 — 19,062 subscribers3 September 2026 — 19,617 subscribers5 September 2026 — 20,261 subscribers8 September 2026 — 20,324 subscribers11 September 2026 — 20,383 subscribers13 September 2026 — 20,552 subscribers14 September 2026 — 21,024 subscribers16 September 2026 — 21,149 subscribers18 September 2026 — 21,376 subscribers25 September 2026 — 22,054 subscribers7 August 202625 September 2026
34 measurements spanning 49 days, net +5,033. 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 16,266–22,809 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
25 Sept 2026, 05:4022,054+678
18 Sept 2026, 18:3621,376+227
16 Sept 2026, 07:3921,149+125
14 Sept 2026, 15:4121,024+472
13 Sept 2026, 03:3720,552+169
11 Sept 2026, 06:4120,383+59
8 Sept 2026, 07:3820,324+63
5 Sept 2026, 01:5920,261+644
3 Sept 2026, 10:0419,617+555
2 Sept 2026, 06:1319,062+3
1 Sept 2026, 03:1319,059+167
31 Aug 2026, 05:0818,892+144
30 Aug 2026, 05:2518,748+188
29 Aug 2026, 02:3818,560+108
28 Aug 2026, 03:1218,452+177
27 Aug 2026, 03:0218,275+186
25 Aug 2026, 23:4618,089+17
25 Aug 2026, 01:4218,072-23
23 Aug 2026, 14:0218,095+94
22 Aug 2026, 01:5818,001first reading

Engagement

55 posts held, back to 17 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 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
69.7%
avg views ÷ 22,054 subscribers
Avg views / post
15,400
13 posts measured
Reaction rate
1.55%
reactions ÷ views · ER floor
Posts in window
13
of 55 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. It is computed over the 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 September 2026
Posts held55 (17 July 2026 – 28 September 2026)
Views total199,744
Reactions total3,099
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 13:38 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

Photos
393
Videos
6
Links
1

Lifetime counters from Telegram’s own channel header, read 29 September 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.

Reaction mix

10,176 reactions across 42 posts, in 33 distinct kinds. The most used accounts for 13.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓1,39813.7%
💋1,28712.6%
❤‍🔥9519.35%
custom 52580801469586176747607.47%
custom 52580909573913043216876.75%
custom 51908809769762466484654.57%
custom 52876712561523051034174.10%
💘3653.59%
custom 58571485548411693333563.50%
custom 53616871491187842533313.25%
custom 52178560731295544102882.83%
custom 51929177793170249802862.81%
custom 52247015552146666472682.63%
custom 58593335464385650432482.44%
custom 59429551036977707022462.42%
😭2382.34%
custom 52515865859037729042092.05%
custom 52874065530228868932082.04%
custom 58729835623906095152042.00%
custom 54161109732389215741981.95%
13 further kinds7667.53%

Custom emoji. 15 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 42 of the 55 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 10,176 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 55 most recent posts we hold, published 17 July 2026 to 28 September 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
49
across the posts below
Posts paid on
16
of 55 we hold a reading for · 29%
Most on one post
20
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Ayooty20. 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 55 most recent posts we hold for this entry, published 17 July 2026 to 28 September 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

28 Sept 2026, 22:00 UTC≈2,360 views153 reactionsread 29 September 2026
Video message

Video message, posted without a caption

custom 525808014695861767487custom 496302797117142126733❤‍🔥19🍓13💘1

25 Sept 2026, 09:12 UTC≈8,280 views191 reactionsread 29 September 2026

‏أحنا بننسى اللي حصل بس مبننساش اللي حسينا فيه ✨

custom 5224701555214666647116❤‍🔥27😭24🍓11💘9💋4

22 Sept 2026, 23:00 UTC≈11,500 views240 reactionsread 29 September 2026
Photo

.✨✨✨✨✨✨✨✨✨✨.

custom 5224701555214666647152❤‍🔥48💘21🍓13😭5💋1

19 Sept 2026, 23:18 UTC≈14,900 views347 reactionsread 29 September 2026
Video message

Video message, posted without a caption

custom 5287671256152305103201🍓50😭45custom 525809095739130432128💋23

16 Sept 2026, 20:00 UTC≈18,300 views319 reactionsread 29 September 2026
Photo

Photo, posted without a caption

❤‍🔥177custom 525808014695861767466🍓32💘22💋19custom 52580909573913043213

14 Sept 2026, 22:40 UTC≈18,200 views266 reactionsread 29 September 2026

أرسلتُ إليها عصفوري لكي يتجسس عليها فَـ أغرتهُ بِـ حُسنها وباحَ لهَا بكل أسراري .🤍

💋134custom 521785607312955441075custom 525158658590377290424🍓18😭15

14 Sept 2026, 22:40 UTC≈20,200 views255 reactions1 Starread 29 September 2026
Photo

🌟

custom 5217856073129554410188❤‍🔥23💋21🍓12custom 525158658590377290411

12 Sept 2026, 09:12 UTC≈21,400 views282 reactions5 Starsread 29 September 2026

مش دايمًا يكون إلندم علشان عملنا حاجة غلط ، مُمكن نندم علشان عملنا حاجة صح بس للشخص الغلط .. 🩷

custom 5416110973238921574198🍓23❤‍🔥19💘14custom 521785607312955441011😭9💋8

7 Sept 2026, 14:50 UTC≈28,200 views293 reactions5 Starsread 29 September 2026
Photo

🌟Skin care 🌟

🍓175custom 536192180465699964376💘17custom 52178560731295544109😭8❤‍🔥5💋3

3 Sept 2026, 23:12 UTC≈28,300 views392 reactionsread 29 September 2026
Photo

.🩷🩷🩷🩷🩷🩷🩷🩷🩷🩷🩷.

custom 5192917779317024980286❤‍🔥41🍓34💋17😭8custom 52178560731295544105💘1

1 Sept 2026, 23:02 UTC≈27,800 views359 reactionsread 29 September 2026

الرحلة مو فردية اللّٰه معك يرعاك تحاوطك رحمته بكل الاحتمالات🌟

custom 5258080146958617674238custom 536187640685268047552🍓37💘19😭13

1 Sept 2026, 10:10 UTC113 views2 reactionsread 1 September 2026

تخبلللللل عبالك بزونةةةة⭐⭐

❤‍🔥2

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

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 51 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“𝙰𝚈𝙾” (@Ayooty20), 22,054 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Ayooty20.

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.