Telegram RegisterThe public register of Telegram
Telegram profile photo for bekenovy

Channel

bekenovy

@bizbknvyy

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

9subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002998358698
TypeChannel
Username@bizbknvyy
Created26 October 2025measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live5 September 2026
Measurements held2
Confirmed unchanged4 times, most recently 5 September 2026
On Telegramt.me/bizbknvyy

Growth

913 Aug 2026, 00:46 — 9 subscribers13 Aug 2026, 23:34 — 9 subscribers13 Aug 2026, 00:4613 Aug 2026, 23:34
2 measurements taken within a single day. 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 23:349no change
13 Aug 2026, 00:469first reading

Engagement

6 posts held, back to 26 October 2025the 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 6 posts for this entry, the most recent from 3 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5422716675889840676420.0%
custom 5422852074733848679420.0%
custom 5269661771085402786315.0%
custom 5217655322063161314210.0%
custom 5269302999582266493210.0%
custom 526935502452112304415.00%
custom 537507747416823856815.00%
custom 537558818443443787915.00%
custom 542025890232954456715.00%
custom 542241446481102729715.00%

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

Measured over the 6 most recent posts we hold, published 26 October 2025 to 3 November 2025, 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

3 Nov 2025, 17:08 UTC295 views5 reactionsread 13 August 2026
File

File, posted without a caption

custom 52696617710854027862custom 54228520747338486792custom 53750774741682385681

28 Oct 2025, 17:14 UTC378 views5 reactionsread 13 August 2026
File

vd.adm - @issahsh

custom 54227166758898406762custom 52176553220631613141custom 52693029995822664931custom 54228520747338486791

26 Oct 2025, 08:26 UTC970 views8 reactionsread 13 August 2026
Photo

B K N 👕 пока мы здесь, сучки хотят нас MAKHAN 🎀

custom 52176553220631613141custom 52693029995822664931custom 52693550245211230441custom 52696617710854027861custom 54202589023295445671custom 54224144648110272971custom 54227166758898406761custom 54228520747338486791

26 Oct 2025, 08:21 UTC490 views2 reactionsread 13 August 2026

- ARCHIVE 💋 с сегодняшнего дня, 08.08.2025, официально заявляем что название кзкф " BEKENOVY ", а так же инициалы " bkn", "bekenov(-a)", "011" принадлежит нам. Если увидим такое же название у других - sgemz

custom 53755881844344378791custom 54227166758898406761

Showing the 6 most recent of 6 posts we hold for @bizbknvyy. 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.

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 2 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“bekenovy” (@bizbknvyy), 9 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/bizbknvyy.

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.