любимая Georgia 🇬🇪
custom 52874415097617011593custom 53482532043814570303custom 54093625874794696623custom 53594301395097568502custom 52895729302320134501

Channel
@aysunkaaaaaa
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry
435subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002050825002 |
|---|---|
| Type | Channel |
| Username | @aysunkaaaaaa |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/aysunkaaaaaa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 23:19 | 435 | +1 |
| 24 Aug 2026, 10:09 | 434 | -2 |
| 8 Aug 2026, 05:16 | 436 | no change |
| 7 Aug 2026, 23:36 | 436 | -1 |
| 7 Aug 2026, 17:14 | 437 | first reading |
13 posts held, back to 17 June 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 13 (17 June 2026 – 7 August 2026) |
| Views total | 258 |
| Reactions total | 51 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:16 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.
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.
291 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 29.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5409362587479469662 | 85 | 29.2% | |
| custom 5287441509761701159 | 82 | 28.2% | |
| custom 5348253204381457030 | 47 | 16.2% | |
| custom 5359430139509756850 | 44 | 15.1% | |
| custom 5289572930232013450 | 33 | 11.3% |
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 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 13 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 291reactions 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 17 June 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @aysunkaaaaaa. 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 17 June 2026 to 7 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.
любимая Georgia 🇬🇪
custom 52874415097617011593custom 53482532043814570303custom 54093625874794696623custom 53594301395097568502custom 52895729302320134501
очень жарко 😭
custom 52895729302320134509custom 53482532043814570303custom 54093625874794696623custom 52874415097617011591custom 53594301395097568501
a trip with Mum 🌊🏝️
custom 52874415097617011599custom 53594301395097568506custom 54093625874794696625custom 52895729302320134501custom 53482532043814570301
6 августа улетаю отдыхать 🙏
custom 54093625874794696627custom 52874415097617011595custom 53482532043814570305custom 52895729302320134502custom 53594301395097568501
наконец-то я узнала, что поступила на бюджет 🥳
custom 528744150976170115912custom 52895729302320134507custom 54093625874794696627custom 53594301395097568502custom 53482532043814570301
🤫
custom 534825320438145703011custom 53594301395097568506custom 54093625874794696624custom 52895729302320134502
испания заберет 🤫
custom 52874415097617011597custom 53482532043814570305custom 53594301395097568503custom 54093625874794696623custom 52895729302320134501
как красиво 😍
custom 540936258747946966210custom 52874415097617011595custom 53594301395097568504custom 52895729302320134501custom 53482532043814570301
😘
custom 528744150976170115910custom 53594301395097568506custom 54093625874794696626custom 53482532043814570302custom 52895729302320134501
на эту укладку 😌
custom 54093625874794696629custom 52874415097617011597custom 53482532043814570306
горжусь любимой Мамой 🥹🤍
custom 540936258747946966213custom 53594301395097568508custom 52874415097617011597custom 52895729302320134505custom 53482532043814570302
🌫️
custom 528744150976170115912custom 54093625874794696627custom 53482532043814570306custom 52895729302320134502
Showing the 12 most recent of 13 posts we hold for @aysunkaaaaaa. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“aysun's blog” (@aysunkaaaaaa), 435 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/aysunkaaaaaa.
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.