23 Apr 2026, 13:13 UTC298 viewsread 14 August 2026
патент за нами
Signed Anelisb
Channel
ZHANAKHANOVY – 077 закрыты
@zhanakhanovyyy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
89subscribers
-16 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002543653683 |
|---|---|
| Type | Channel |
| Username | @zhanakhanovyyy |
| Created | 13 May 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/zhanakhanovyyy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 02:01 | 89 | -1 |
| 7 Sept 2026, 23:41 | 90 | -5 |
| 29 Aug 2026, 04:12 | 95 | -3 |
| 22 Aug 2026, 21:24 | 98 | -6 |
| 15 Aug 2026, 19:34 | 104 | -1 |
| 14 Aug 2026, 23:45 | 105 | no change |
| 14 Aug 2026, 23:32 | 105 | first reading |
Engagement
4 posts held, back to 13 May 2025 — 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 4 posts for this entry, the most recent from 23 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 30s
- Average length
- 30s
Measured directly from 1 video 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.
Reaction mix
31 reactions across 2 posts, in 12 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249336757480092708 | 10 | 32.3% | |
| custom 5370724984375230762 | 7 | 22.6% | |
| custom 5199601525818676610 | 2 | 6.45% | |
| custom 5199825229190286349 | 2 | 6.45% | |
| custom 5210821354785363278 | 2 | 6.45% | |
| custom 5219879629791188166 | 2 | 6.45% | |
| custom 5240405385872955233 | 1 | 3.23% | |
| custom 5267403301187504967 | 1 | 3.23% | |
| custom 5332721030681088300 | 1 | 3.23% | |
| custom 5348451790784323741 | 1 | 3.23% | |
| custom 5391352591311466466 | 1 | 3.23% | |
| custom 5442621654578522837 | 1 | 3.23% |
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 2 of the 4 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 13 May 2025 to 23 April 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
29 Oct 2025, 13:07 UTC≈3,950 views17 reactionsread 14 August 2026
Video
🔠 WELCOME TO ZHANAKHANOVY – 077😈 ➿➿➿➿➿➿➿➿➿➿➿➿➿ “I don’t compete, I make it uncomfortable for others to exist near me”🎲 ➿➿➿➿➿➿➿➿➿➿➿➿➿ INFO ⭐️ ADM ⭐️ RULES ⭐️ INT ⭐️ BOO$T ⭐️ UNION ⭐️ТТ ⭐️
custom 524933675748009270810custom 52198796297911881662custom 52404053858729552331custom 53327210306810883001custom 53484517907843237411custom 53913525913114664661custom 54426216545785228371
Signed aas 77
13 May 2025, 17:14 UTC≈1,570 views14 reactionsread 14 August 2026
Photo
PATENT - ZHANAHANOVYY 🌟 С 13.05.25,мы официально заявляем что название «Zhanakhanovyy» принадлежит только нам. Если мы увидим такое же название,то мы имеем полное право попросить изменить вас название.В случае где будут говорить «Мы открылись раньше,не будем менять» не принимаются,так как мы всё подтверждаем патентом. 13.05.25 ✅
custom 53707249843752307627custom 51996015258186766102custom 51998252291902863492custom 52108213547853632782custom 52674033011875049671
13 May 2025, 16:54 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @zhanakhanovyyy. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“ZHANAKHANOVY – 077 закрыты” (@zhanakhanovyyy), 89 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zhanakhanovyyy.
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.