· кстати, я получила еще зеленький стакан, синий мне передали и остался последний оранжевый 😇
custom 51974948615398704982custom 52535596423399723711custom 53439684591076216671custom 53728522687920549851

Channel
@anoramew
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
166subscribers
-7 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002366594084 |
|---|---|
| Type | Channel |
| Username | @anoramew |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/anoramew |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 14:16 | 166 | -2 |
| 17 Aug 2026, 18:56 | 168 | -5 |
| 11 Aug 2026, 09:01 | 173 | no change |
| 11 Aug 2026, 08:49 | 173 | first reading |
10 posts held, back to 2 August 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 10 (2 August 2026 – 9 August 2026) |
| Views total | 464 |
| Reactions total | 47 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 09:01 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.
47 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 29.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5197494861539870498 | 14 | 29.8% | |
| custom 5253559642339972371 | 9 | 19.1% | |
| custom 5192789076327045305 | 6 | 12.8% | |
| 💘 | 6 | 12.8% | |
| custom 5343968459107621667 | 5 | 10.6% | |
| custom 5193174854584536287 | 2 | 4.26% | |
| custom 5372852268792054985 | 2 | 4.26% | |
| custom 5193200723172550943 | 1 | 2.13% | |
| custom 5375286046370064493 | 1 | 2.13% | |
| custom 5384330083559290327 | 1 | 2.13% |
Custom emoji. 9 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 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 9 of the 10 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 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 2 August 2026 to 9 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.
· кстати, я получила еще зеленький стакан, синий мне передали и остался последний оранжевый 😇
custom 51974948615398704982custom 52535596423399723711custom 53439684591076216671custom 53728522687920549851
· посмотрите какой он пирожочечек🤭🍧
custom 51974948615398704982custom 53439684591076216672custom 51927890763270453051custom 53843300835592903271
Video message, posted without a caption
custom 51974948615398704985💘2custom 52535596423399723712
· моя первая жертва ❤️❤️❤️
custom 51931748545845362872custom 52535596423399723711custom 53439684591076216671
· я ночью уснула, не успела кинуть блен и весь день с утра занята была(
💘2custom 52535596423399723712custom 53439684591076216671
Video message, posted without a caption
· ребзи, маски в закрепе по косарю каждая🎀 заберите кто-нибудь, мне с ними нечего делать
custom 51974948615398704981custom 52535596423399723711
· бляо готовка именно так ощущается🙁🫠 короче вот итог, можно считать что я справилась, по вкусу очень легким получился кстати, неплохо вышло🍓
custom 51974948615398704983custom 52535596423399723711custom 53728522687920549851
· это пищдец, я пока крошила печенюшки в сливки, в них откуда то появилась вода и они начали чуть-чуть расслаиваться и за ночь эта жижа растеклась по тарелке😭 + мне не хватило их, седня буду пытаться исправить все это...
custom 51927890763270453055custom 51974948615398704981custom 53752860463700644931
Video message, posted without a caption
💘2custom 51932007231725509431custom 52535596423399723711
Showing the 10 most recent of 10 posts we hold for @anoramew. 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.
Citation-graph rank — 601,034 of 1,628,524entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“-°𝘢𝘯𝘰𝘳𝘢.𝘮𝘦𝘸” (@anoramew), 166 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/anoramew.
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.