Channel
@aynosrewersee
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
90subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002094557260 |
|---|---|
| Type | Channel |
| Username | @aynosrewersee |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 4 September 2026 |
| On Telegram | t.me/aynosrewersee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 01:54 | 90 | -1 |
| 9 Aug 2026, 14:16 | 91 | no change |
| 7 Aug 2026, 12:55 | 91 | first reading |
9 posts held, back to 23 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 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 9 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
64 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5253694757716120719 | 16 | 25.0% | |
| custom 5213450944217369976 | 10 | 15.6% | |
| custom 5242631308508680087 | 9 | 14.1% | |
| custom 5346255348804108701 | 8 | 12.5% | |
| custom 5242720124137393566 | 7 | 10.9% | |
| custom 5359770382523974625 | 6 | 9.38% | |
| custom 5366575685190044931 | 5 | 7.81% | |
| custom 5463022543076085411 | 3 | 4.69% |
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 9 of the 9 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 23 June 2026 to 30 July 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.
мы хотели покормить уточек, но рядом был тока клевер….А КОГДА МЫ ПОШЛИ ЗА ХЛЕБОМ, ТО НАС ВЫГНАЛИ ИЗ-ЗА ТОГО, ЧТО ПАРК ЗАКРЫВАЛСЯ…😭
custom 52536947577161207192custom 52134509442173699761custom 52426313085086800871custom 52427201241373935661custom 53462553488041087011custom 53665756851900449311
эм, шарите, 92 без очереди📞
custom 52426313085086800871custom 52427201241373935661custom 52536947577161207191custom 53462553488041087011
🤩мы ездили в крутое место с ночевкой в палатках, крутые??????
custom 52426313085086800871custom 52427201241373935661custom 52536947577161207191custom 53462553488041087011
🍵📸🌳мы катались на лодке (через 6 часов, когда мы возвращались домой начался сильный ливень с грозой, МОЛНИЯ БИЛА В РЕКУ, В МЕСТО НЕПОДАЛЕКУ ОТ НАС И МЫ, КАК КРУТЫЕ ВЫЖИЛИ) мы целый час плыли в надежде, чтобы нас не ударило молнией)))))))))))
custom 52134509442173699761custom 52427201241373935661custom 53597703825239746251
🌟эта мы позавчера друга с армейки встречали
custom 52134509442173699761custom 52426313085086800871custom 52427201241373935661custom 52536947577161207191
проснуться популярной✅
custom 52134509442173699766custom 52536947577161207196custom 53597703825239746254custom 52427201241373935661custom 53462553488041087011custom 54630225430760854111
🤍🏃пополнение ml
custom 54630225430760854112custom 52426313085086800871custom 52536947577161207191custom 53462553488041087011custom 53597703825239746251custom 53665756851900449311
Video message, posted without a caption
custom 53462553488041087013custom 52426313085086800872custom 52536947577161207192custom 52134509442173699761custom 52427201241373935661custom 53665756851900449311
босс кпк
custom 52426313085086800872custom 52536947577161207192custom 53665756851900449312
Showing the 9 most recent of 9 posts we hold for @aynosrewersee. 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.
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.
“𝓼𝓸𝓷𝓮𝓬𝓱𝓴𝓪 𝓪𝔂𝓷𝓸𝓼𝓻𝓮𝔀𝓮𝓻𝓼𝓮” (@aynosrewersee), 90 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/aynosrewersee.
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.