6 measurements spanning 38 days, net -14. 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 387–405 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Sept 2026, 23:59
389
-3
29 Aug 2026, 09:34
392
-2
22 Aug 2026, 23:52
394
-2
14 Aug 2026, 20:28
396
-6
7 Aug 2026, 19:28
402
-1
6 Aug 2026, 23:47
403
first reading
Engagement
13 posts held, back to 20 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 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 13 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
746 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 49.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5235928522416990466
371
49.7%
custom 5350357274500016610
124
16.6%
custom 5350812854566002510
110
14.7%
🍓
77
10.3%
💘
64
8.58%
Custom emoji. 3 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 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 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 746 reactions 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 20 July 2026 to 2 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.
Telegram Stars
Stars received
57
across the posts below
Posts paid on
8
of 13 we hold a reading for · 62%
Most on one post
18
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bzrky. 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 20 July 2026 to 2 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.
🤩🤩🤩🤩 🤩🤩🤩
➡️цензурная версия!!
писать: @lesliechlen ←←
➖➖➖➖➖➖➖➖➖
↖️цена 💗💗 500р
✅ можно менять (бесплатно!):
🎀цвета (любая палитра)
🎀прическа
🎀эмоция
🎀аксессуары и любые мелкие детали!
🎀 предмет сосания (заменить на
игрушку, или любой другой предмет
схожей формы, поменять цвет и размер)
❌ НЕ рисую
🎀детей
🎀животных (неко и фурри, не сильно отличающиеся формой головы от
человека, и подобные существа — ок ✅)
🎀насто…
➡️🤩🤩🤩🤩🤩🤩🤩🤩
в рандомных стилях!
🍥🍥🍥🍥🍥🍥🍥🤩
🌟 подписка на меня
🌟 репост в тгк / двум друзьям
🌟 скинуть в коммы пруфы репоста и персонажа вместе с именем !!
➡️ я помещу всех персонажей в рулетку, и рандомно выберу одного или нескольких, а после точно так же рандомно выберу стиль одежды из другой рулетки ! 🥰 начну когда наберётся минимум 5 персонажей, максимум от одного человека — 2, но если я уже рисовал вашего…
Showing the 12 most recent of 13 posts we hold for @bzrky. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
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 13 September 2026 — this
entry's latest reading, not the date you are reading this.
“безрукий унба” (@bzrky), 389 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/bzrky.
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.
