Telegram RegisterThe public register of Telegram

Channel

Банаnka

@ankanesk

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

132subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001834558956
TypeChannel
Username@ankanesk
CreatedBetween 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/ankanesk

Growth

132133132.58 Aug 2026, 11:19 — 133 subscribers9 Aug 2026, 00:17 — 133 subscribers9 Aug 2026, 05:50 — 132 subscribers8 Aug 2026, 11:199 Aug 2026, 05:50
3 measurements taken within a single day, net -1. 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 132–133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 05:50132-1
9 Aug 2026, 00:17133no change
8 Aug 2026, 11:19133first reading

Engagement

16 posts held, back to 21 May 2026the 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 · 30 days
107.8%
avg views ÷ 132 subscribers
Avg views / post
142
6 posts measured
Reaction rate
8.78%
reactions ÷ views · ER floor
Posts in window
6
of 16 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held16 (21 May 20266 August 2026)
Views total854
Reactions total75
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 00:17 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.

Reaction mix

262 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 35.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54158856034199997699435.9%
custom 58479299229363787425420.6%
custom 52853458405991510913914.9%
custom 53080412595400373652911.1%
custom 5413540920643570381259.54%
custom 5309850527398377919134.96%
custom 541333072923907355583.05%

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 16 of the 16 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 262reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 21 May 2026 to 6 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.

Recent posts

6 Aug 2026, 05:44 UTC171 views6 reactionsread 9 August 2026
Photo

✨✨✨✨✨✨✨✨✨✨✨ Вернёмся в беззаботное детство?✨ ✨Ивент: «Верни краски!» ✨Суть проста: организатор раздаёт участникам арт без лайна, раскинутый по секциям (квадратам). Участники по очереди их заполняют. Проще говоря: картина по номерам, только немного проще! ✨Для участия: ✨Подписка на канал ✨Репост в свой канал; пиар чат или друзьям с пруфами! ✨Скинуть пару работ и свой тгк (при наличии) и написать свой порядковый н

custom 52853458405991510914custom 54158856034199997692

31 Jul 2026, 11:35 UTC119 views19 reactionsread 9 August 2026
Photo

Лёгкий спойлер того, что будет в будущем🤩 #скетя

custom 54158856034199997698custom 52853458405991510917custom 53080412595400373654

30 Jul 2026, 13:45 UTC102 views17 reactionsread 9 August 2026
Photo

Разные почеркуши с секайцами и скрин с титулом с главы Руи #скетя

custom 54158856034199997697custom 52853458405991510915custom 53080412595400373655

25 Jul 2026, 11:14 UTC147 views11 reactionsread 9 August 2026
Photo

Апдееейт, у меня получилось! #флуд

custom 58479299229363787429custom 53080412595400373652

24 Jul 2026, 14:00 UTC135 views10 reactionsread 9 August 2026
Photo

Завтра закончатся страдания, завтра... Энергия заканчивается, чорт, держусь мизинцами за т2к😫 Мне походу не хватило мучений с Руи6.. #флуд

custom 58479299229363787425custom 54158856034199997693custom 54133307292390735552

16 Jul 2026, 07:24 UTC180 views12 reactionsread 9 August 2026
Photo

Чета у меня снова руки завязались(( но раз в месяц постараюсь чета накалякать В комментариях котики #флуд

custom 541354092064357038110custom 52853458405991510912

11 Jul 2026, 19:13 UTC192 views19 reactionsread 9 August 2026
Photo

Даже котёнку понравился Руи🌟 #щитпост

custom 58479299229363787429custom 54158856034199997697custom 52853458405991510913

7 Jul 2026, 18:18 UTC179 views13 reactionsread 9 August 2026
Photo

Прикольная штука, ориг в комментариях🐬 Скидывайте, кстати, своих тоже с этим шаблоном! Мне очень интересно узнать, что вы думаете насчёт Румбы? Какой персонаж она для вас? #ос #скетя #флуд

custom 54158856034199997696custom 53080412595400373654custom 54133307292390735553

24 Jun 2026, 07:23 UTC223 views17 reactionsread 9 August 2026
Photo

С днём рождения, Руи!🌟 Думаю, не закончу эту работу, но выложу как есть.. #скетя

custom 54158856034199997698custom 53080412595400373654custom 52853458405991510912custom 58479299229363787422custom 54135409206435703811

14 Jun 2026, 06:28 UTC230 views20 reactionsread 9 August 2026
Photo

Кітікі🤸 #флуд

custom 541588560341999976911custom 53098505273983779199

13 Jun 2026, 19:05 UTC214 views10 reactionsread 9 August 2026
Forwarded from @krokopopaPhoto

📟Действительно думала что сумеешь скрыться от меня? Не забывай на что мы способны 📠  📹Рунар - одна из многих исполнителей разведывательной деятельности корпорации "wasps". Тщательно все обдумайте прежде чем начинать сотрудничество, а если уж соблазнились, то выложитесь по полной, иначе это может плохо кончиться. Будьте начеку, иначе хитрая лисичка не побрезгует обнажит свои коготки. ⛓️Удачных вам голодных игр. ⛓️

custom 54135409206435703816custom 54158856034199997694

12 Jun 2026, 21:34 UTC221 views20 reactionsread 9 August 2026
Photo

Когда режиссер теряет контроль над собственным разумом, шоу превращается в казнь. 💅💅 #арт

custom 53080412595400373658custom 54135409206435703816custom 54133307292390735553custom 54158856034199997693

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

Citation-graph rank — 349,901 of 1,151,006entries 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.

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

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

“Банаnka” (@ankanesk), 132 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ankanesk.

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.