Telegram RegisterThe public register of Telegram
Telegram profile photo for ⏜۫︵۫ ⣦ 𝗞݊ꪀ𝗬 𝗰𝘂𝘁ׅ꯱ ⣴꯭ ׁ ⸼ | нарезки крд

Channel

⏜۫︵۫ ⣦ 𝗞݊ꪀ𝗬 𝗰𝘂𝘁ׅ꯱ ⣴꯭ ׁ ⸼ | нарезки крд

@knycuts

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

81subscribers

+9 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-1003471732289
TypeChannel
Username@knycuts
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/knycuts

Growth

728779.58 August 2026 — 72 subscribers9 August 2026 — 72 subscribers16 August 2026 — 79 subscribers22 August 2026 — 87 subscribers29 August 2026 — 86 subscribers6 September 2026 — 81 subscribers818 August 20266 September 2026
6 measurements spanning 29 days, net +9. 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 70–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 01:4281-5
29 Aug 2026, 05:0486-1
22 Aug 2026, 14:1387+8
16 Aug 2026, 03:0479+7
9 Aug 2026, 22:4772no change
8 Aug 2026, 10:0072first reading

Engagement

20 posts held, back to 13 July 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 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

43 reactions across 7 posts, in 11 distinct kinds. The most used accounts for 18.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5384240563555960157818.6%
custom 5379657893580671294614.0%
custom 5384533299936923036614.0%
614.0%
❤‍🔥511.6%
custom 539542023457841520836.98%
custom 539791798998927338936.98%
💯36.98%
custom 537968987820212417412.33%
🍓12.33%
🔥12.33%

Custom emoji. 6 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 7 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 43 reactions 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 13 July 2026 to 9 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

9 Aug 2026, 07:45 UTC15 viewsread 9 August 2026
Forwarded from @hakoyukiakayukicfdailyVideo

❤️. 🥹桜の花🥹🥹🤩𝙚𝙡𝙘𝙤𝙢𝙚!! 🐱 . 🌸🤩🤩🤩 𝑡ℎ𝑖𝑠 𝑖𝑠 𝑠𝑜𝑦𝑎𝑚𝑎 𝑑𝑎𝑖𝑙𝑦 - 𝑐𝑓❗️ . 𝗞𝗜𝗠𝗘𝗧𝗦𝗨 𝗡𝗢 𝗬𝗔𝗜𝗕𝗔 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🔤ак хочешь найти контент по этому пейрингу, обсудить его динамику и полюбоваться творчеством по нему? 🔼🔤е пропускай же время, иди к нам !! 🤩🤩 . 🩷 🤍🤍🤍🤍🤍🤍 https://t.me/hakoyukiakayukicfdaily https://t.me/hakoyukiakayukicfdaily https://t.me/hakoyukiakayukicfdaily

7 Aug 2026, 16:45 UTC48 views1 reactionsread 9 August 2026

𝆹𝅥𝆹𝅥 ꯭ֺ ⊹ ִ ׁ 🌟dmin Search 𝇄ִ ۫🤩 𝅄𝅄 ִ ゙ 🤩🤩– анкета будет указана ниже, писать в комментарии. ❌ Имею право отказать, не называя причины, а также, если вы вовсе не имеете опыта и представления об этом. ❌ 🥹 Ваш псевдоним, местоимения, маскот, юзер. 🥹 Должность в администрации: впшер/админ по вырезке. 🥹 Был ли у вас опыт в вп или нарезках? (необязательно). 🥹 Как часто вы можете пропадать, сколько примерно за неделю

custom 53796898782021241741

5 Aug 2026, 04:26 UTC86 views7 reactionsread 9 August 2026

𝅄۫ ꯭ ◌⃘🤩 𝖼υׁׅ𝗍꯱ ִ ⸼ ˖ ִ ੭੭ֺ ○ #накиме 𓍟゙ ִ @knycuts _ 𝗕𝗢𝗢𝗦𝗧 _ 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 нарезки находятся в комментариях.

custom 53796578935806712942custom 53842405635559601572custom 53845332999369230361custom 53954202345784152081custom 53979179899892733891

3 Aug 2026, 13:01 UTC112 views3 reactionsread 9 August 2026

𝅄۫ ꯭ ◌⃘🤩 𝖼υׁׅ𝗍꯱ ִ ⸼ ˖ ִ ੭੭ֺ ○ #руи 𓍟゙ ִ @knycuts _ 𝗕𝗢𝗢𝗦𝗧 _ 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 нарезки находятся в комментариях.

custom 53842405635559601571custom 53954202345784152081custom 53979179899892733891

20 Jul 2026, 01:14 UTC214 views10 reactionsread 9 August 2026

𝅄۫ ꯭ ◌⃘🤩 𝖼υׁׅ𝗍꯱ ִ ⸼ ˖ ִ ੭੭ֺ ○ #мудзан 𓍟゙ ִ @knycuts _ 𝗕𝗢𝗢𝗦𝗧 _ 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 нарезки находятся в комментариях.

custom 53796578935806712942custom 53842405635559601572custom 538453329993692303621❤‍🔥1🍓1🔥1

19 Jul 2026, 23:50 UTC211 views6 reactionsread 9 August 2026

𝅄۫ ꯭ ◌⃘🤩 𝖼υׁׅ𝗍꯱ ִ ⸼ ˖ ִ ੭੭ֺ ○ #умэ 𓍟゙ ִ @knycuts _ 𝗕𝗢𝗢𝗦𝗧 _ 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗼𝗻 нарезки находятся в комментариях.

1❤‍🔥1💯1custom 53796578935806712941custom 53842405635559601571custom 53845332999369230361

Showing the 12 most recent of 20 posts we hold for @knycuts. 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 1 registered channel — 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“⏜۫︵۫ ⣦ 𝗞݊ꪀ𝗬 𝗰𝘂𝘁ׅ꯱ ⣴꯭ ׁ ⸼ | нарезки крд” (@knycuts), 81 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/knycuts.

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.