Sticker, posted without a caption

Channel
﹝𝐋𝖎𝖋𝖊﹞ ❛❛ 𝒜𝐞𝗿𝝸𝐬᪾ ❜❜
@AES_LIF
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
175subscribers
+15 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003425715790 |
|---|---|
| Type | Channel |
| Username | @AES_LIF |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/AES_LIF |
Previous handles
@AES_LIF was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 10 August 2026 – 10 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 01:18 | 175 | +2 |
| 15 Sept 2026, 04:22 | 173 | no change |
| 15 Sept 2026, 03:47 | 173 | +25 |
| 25 Aug 2026, 12:04 | 148 | -5 |
| 18 Aug 2026, 04:11 | 153 | -7 |
| 10 Aug 2026, 23:00 | 160 | no change |
| 10 Aug 2026, 22:50 | 160 | first reading |
Engagement
40 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 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 26.6%
- avg views ÷ 175 subscribers
- Avg views / post
- 46.5
- 19 posts measured
- Reaction rate
- 8.52%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 40 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 6 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 September 2026 |
|---|---|
| Posts held | 40 (17 July 2026 – 14 September 2026) |
| Views total | 883 |
| Reactions total | 26 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Sept 2026, 04:22 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
- 28s
- Average length
- 28s
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
62 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 19.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5438624826732357463 | 12 | 19.4% | |
| custom 5440660692770267614 | 11 | 17.7% | |
| custom 5429159311517448996 | 8 | 12.9% | |
| custom 5440491801771286427 | 6 | 9.68% | |
| custom 5274219336976869407 | 5 | 8.06% | |
| custom 5422455550468193436 | 5 | 8.06% | |
| custom 5321161697434569259 | 4 | 6.45% | |
| custom 5429574201063279918 | 3 | 4.84% | |
| custom 5269656093138644314 | 2 | 3.23% | |
| custom 5273869340091920631 | 2 | 3.23% | |
| custom 5440389242247222977 | 2 | 3.23% | |
| custom 5271812621987787499 | 1 | 1.61% | |
| custom 5292220442562552933 | 1 | 1.61% |
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 13 of the 40 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 62 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 17 July 2026 to 14 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
- 10
- across the posts below
- Posts paid on
- 1
- of 37 we hold a reading for · 3%
- Most on one post
- 10
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @AES_LIF. 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 40 most recent posts we hold for this entry, published 17 July 2026 to 14 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
» 𝐏𝖊𝖆𝔯𝔩🤩🤩 ︎︎ ︎::если до завтрашнего вечера закроете ВЕЕСЬ набор то некоторым сделаю доп в формате какой вы эстетичный десерт. ::или всем? #shpAS
custom 54291593115174489961
Sticker, posted without a caption
Sticker, posted without a caption
💐🤩🤍 в этот день наши ладони с " 𝗴𝗮𝗹𝗮𝘅𝘆'𝘀 𝗲𝗱𝗴𝗲 " перекрыли друг-друга, а нити на запястьях стали точкой невозврата.🤩 🤩🤩 𝓌hat time is it now? i want to remember this time of day when i fell in love again. 🤍 🕯 𝗜𝗡𝗙𝗢 : @infoGalaxysEdge🤍 👠 𝗟𝗜𝗙𝗘 : @lifeGalaxysEdge🤍 #unionAS
Sticker, posted without a caption
Sticker, posted without a caption
💐🤩🤍 в этот день наши ладони с " 𝑓𝑎𝑢𝑥 𝑔𝑙𝑒𝑒 " перекрыли друг-друга, а нити на запястьях стали точкой невозврата.🤩 🤩🤩 𝓌hat time is it now? i want to remember this time of day when i fell in love again. 🤍 🕯 𝗜𝗡𝗙𝗢 : @fgaluexeINFO🤍 👠 𝗟𝗜𝗙𝗘 : @fgaluexeLIFE🤍 #unionAS
Sticker, posted without a caption
» 𝐎𝖉𝖊𝖙𝔱𝔢 🌟 :: Желаю доброе утро всем Кроме тех... • кто пришёл ко второму. • кто болел ветрянкой. #rubricAS
custom 52742193369768694071custom 54291593115174489961
Sticker, posted without a caption
» 𝐏𝖊𝖆𝔯𝔩🤩🤩 :: подписчики обгоняют союзников искра, одетта, мы точно в своей жизни делаем что-то не так 🌟 :: про участников вообще молчу 🤩🤩 :: ХАХАХА #shpAS
custom 53211616974345692591
Showing the 12 most recent of 40 posts we hold for @AES_LIF. 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.
Mentions
Named by 7 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.
@AES_INF · 2291 post﹝𝐔𝖓𝖎𝖔𝖓𝖘﹞❛❛ 𝒜𝐞𝗿𝝸֟፝ؖ𝐬᪾ ❜❜
@AES_unions · 101 post𝘀𝘂𝗻𝗱𝗮𝘆 𝘂𝗻𝗶𝗼𝗻
@ED_sundayunion · 31 post𝑓𝑎𝑢𝑥 𝑔𝑙𝑒𝑒 🂱 - 𝑼𝑵𝑰𝑶𝑵𝑺
@fgaluexeCLLB · 51 postㅤ🎀ㅤִ ❛❛۟. 𝐔𝐍𝐈𝐎𝐍𝐒 ͘ ۪命 . .
@OR1GAM1_UN1ONS · 321 postLife "Panty, Stocking with Gartebelt flood"
@pantyandstockingfloodlife · 441 postᴸᶦˢᵗ ᵒᶠ ᵘᶰᶦᵒᶰ ᨳ ִ ˖𝗛𝕚𝗴h͟͟𝗲𝗿 𝔒𝗿𝕕e͟͟𝗿 ദ
@UnionHigherOrder · 61 post
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“﹝𝐋𝖎𝖋𝖊﹞ ❛❛ 𝒜𝐞𝗿𝝸𝐬᪾ ❜❜” (@AES_LIF), 175 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/AES_LIF.
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.