Telegram RegisterThe public register of Telegram

Channel

Архивировано | Кнай sекsовичʰᵈˢᵐˢᶞᵈ

@Knay_bots

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

79subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002627649145
TypeChannel
Username@Knay_bots
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/Knay_bots

Growth

7910 Aug 2026, 10:30 — 79 subscribers10 Aug 2026, 19:27 — 79 subscribers10 Aug 2026, 10:3010 Aug 2026, 19:27
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 78–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 19:2779no change
10 Aug 2026, 10:3079first reading

Engagement

20 posts held, back to 23 August 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
179.7%
avg views ÷ 79 subscribers
Avg views / post
142
1 post measured
Reaction rate
0.704%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 30 July 2026
Posts held20 (23 August 202530 July 2026)
Views total142
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 10:30 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.

What this channel posts

Video runtime
27s
Average length
27s

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

243 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 23.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍌5623.0%
custom 54517334706466642784819.8%
🤮3213.2%
custom 54539848882082585822510.3%
🕊177.00%
💘135.35%
🙏124.94%
114.53%
🎄93.70%
🍾72.88%
🏆62.47%
31.23%
🐳20.823%
❤‍🔥10.412%
🤡10.412%

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

Measured over the 20 most recent posts we hold, published 23 August 2025 to 30 July 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
320
across the posts below
Posts paid on
6
of 18 we hold a reading for · 33%
Most on one post
126
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Knay_bots. 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 20 most recent posts we hold for this entry, published 23 August 2025 to 30 July 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.

Recent posts

30 Jul 2026, 23:08 UTC142 views1 reactionsread 10 August 2026

Блсьь https://t.me/Knaynotbots

🍌1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

30 Jul 2026, 22:53 UTCviews —

Channel name was changed to «Архивировано | Кнай sекsовичʰᵈˢᵐˢᶞᵈ»

31 Jan 2026, 11:09 UTC190 views1 reactionsread 10 August 2026

Ладно, я умер

🍌1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

31 Jan 2026, 11:02 UTCviews —

Channel name was changed to «Закрыто | Кнай sекsовичʰᵈˢᵐˢᶞᵈ»

31 Jan 2026, 11:02 UTC188 views1 reactionsread 10 August 2026
Sticker

Sticker, posted without a caption

🍌1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

31 Jan 2026, 11:01 UTC179 views28 reactionsread 10 August 2026

Ладно, я слишком долго оттягивал момент и сомневался, если честно очень не хочется оставлять это все в прошлом, но всё хорошее когда-нибудь заканчивается. Я очень благодарен всем, кто был рядом и тем, кто остался. Как вы уже поняли, я хочу закрыться. Как бы я не пытался начинать, сейчас я оставляю всё на полпути и как раньше не могу сидеть часами. Спасибо, что стали частью моей жизни, возможно ещё вернусь, люблю вас.

🍌11🕊7🤮5🙏4🐳1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

16 Oct 2025, 16:01 UTC643 views30 reactions55 Starsread 10 August 2026
Photo

◃◃ Dark Party ▹▹ 𝘊𝘰𝘭𝘭𝘢𝘣 𝘸𝘪𝘵𝘩 ► @hzz_twicherskay @CHESTER_BYXAET Читать тут 𝘛𝘞 → Упоминание ревности, "особенная дружба", контент для взрослых, 18+ содержание, намёки на секс. Упоминание спиртных напитков, чрезмерное употребление алкоголя. Недопустимое поведение на мероприятии, возможные неприятные моменты для прочтения, намёк на употребление табачных изделий, намёки на ласки.

🍌13custom 54517334706466642789🙏4🍾1🏆1🐳1custom 54539848882082585821

Signed Zucken🚩 #святойотециван.

13 Oct 2025, 16:13 UTC375 views7 reactionsread 10 August 2026

Довольно объёмная работа, которую я не мог закончить ещё с начала лета, спасибо мандарину, что взялся за коллаб

custom 54517334706466642786🍌1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

13 Oct 2025, 16:12 UTC531 views31 reactions50 Starsread 10 August 2026
Photo

◃◃ По пути ▹▹ 𝘊𝘰𝘭𝘭𝘢𝘣 𝘸𝘪𝘵𝘩 ► @life_ofmandarin Читать тут 𝘛𝘞 → курение, нецензурная лексика 1/1 #Кашенцовы #зарисовка

custom 545173347064666427811🤮8custom 54539848882082585827🎄31🍌1

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

21 Sept 2025, 06:14 UTC353 views17 reactionsread 10 August 2026
Forwarded from @wce08

к сожалению наш товарищ, любимый мью, любимый зарисовчик и просто любимый человек потерялся.. мы любили тебя кнай(максим). легенда навсегда. f. 💘-f... легенда... 🍌-да похуй

🍌11custom 54517334706466642784🍾1custom 54539848882082585821

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

11 Sept 2025, 13:13 UTC494 views44 reactions71 Starsread 10 August 2026
Photo

◃◃ Может, потому что живой? ▹▹ 𝘊𝘰𝘭𝘭𝘢𝘣 𝘸𝘪𝘵𝘩 ► @life_ofmandarin Читать тут 𝘛𝘞 → курение, наркотики, нецензурная лексика, упоминание никрофилии 1/2 #Лидинты #зарисовка

🤮1710🎄6custom 54539848882082585825custom 54517334706466642784🍾2

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

6 Sept 2025, 11:12 UTC390 views2 reactionsread 10 August 2026
Photo

ЕПТВАЮ МАТЬ СПАСИБО

custom 54539848882082585822

Signed Knay #Тынᴇɯᴀᴩиɯь #Дᴏᴧᴦи

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

Citation-graph rank

Citation-graph rank — 176,662 of 1,169,250entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 3 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.

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

“Архивировано | Кнай sекsовичʰᵈˢᵐˢᶞᵈ” (@Knay_bots), 79 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Knay_bots.

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.