Channel
@KKYYDSNB66
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
563subscribers
+35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002785044476 |
|---|---|
| Type | Channel |
| Username | @KKYYDSNB66 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/KKYYDSNB66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 17:39 | 563 | +35 |
| 7 Aug 2026, 07:02 | 528 | no change |
| 7 Aug 2026, 06:51 | 528 | first reading |
10 posts held, back to 1 March 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 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 10 (1 March 2026 – 27 July 2026) |
| Views total | 30 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 07:02 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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 🖕 | 1 | 50.0% |
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 10 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 1 March 2026 to 27 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.
KK·相思MOD合体所有版本 1.0天使神版本❤️❤️❤️❤️ ﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉ 👀👀👀👀👀👀👀👀👀👀👀👀 ⭐天使神第一版本解决所有问题 ⭐适配所有手机系统 ⭐完美解决线上线下所有问题 ⭐更换UI ⭐更换骨骼增加头部绘制 ⭐更换显示人数更加美观 ⭐稳定奔放 ﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉ 🔘追踪局内开启不然会闪退 🔘对局结束之后把追踪关闭到下局局内开启 ﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉ 密钥🔥：KKXSY1F56D80D5D05121310F1E5A210C 安装包下载点击我 😀😀 @KK666YYDSNB @XSMODWD 反馈联系: @XYovOzzz ✔️
🖕1
Signed 自信
防录屏，加vk渲染，小学生喜欢嘛
Signed 自信
KK公益直装MOD （4.3版本）V5版本 📣📣📣📣📣📣 😙更新内容: 😄增加全新美化 😄适配4服 😄增加淘汰播报 Ui及功能查看 👉 @KK666YYDSNB 😍😍😍 @zixinnb
Signed 自信
VT_HOOK_SHADOW((void **)GameViewport->VTable, 133, _PostRenderHook, orig_PostRenderOriginal); 泛滥某知名项目的虚标，垃圾东西还圈钱？ 泛滥频道 @KK666YYDSNB
Signed 自信
KK公益直装MOD （4.3版本）V5版本 📣📣📣📣📣📣 😙更新内容: 😄增加全新美化 😄适配4服 😄增加淘汰播报 Ui及功能查看 👉 @KK666YYDSNB 😍😍😍 @zixinnb
❤1
Signed 自信
KK公益直装MOD （4.3版本）V5版本 📣📣📣📣📣📣 😙更新内容: 😄增加全新美化 😄适配4服 😄增加淘汰播报 Ui及功能查看 👉 @KK666YYDSNB 😍😍😍 @zixinnb
Signed 自信
KK 公益直装_V6.0.apk 1️⃣音量键控制悬浮窗 2️⃣大厅出ui 功能介绍➖➖ 1️⃣KK直装采用裸奔渲染 2️⃣美化采用秒刷美化 3️⃣增加手雷抛物线 ✅更换ios同款绘图 ✅增加内存功能 ✅修复容器闪退 官方频道 @KK666YYDSNB
Signed 自信
估计大家都听说了某牢六要点我tg 频道，也就在昨天晚上他就说要点我频道，我跟他算是在24年的时候认识的，当时玩的也挺好，那年暑假的时候我跟他经常聊天，然后当时我也要中考没时间跟他们那一群玩，就只更新自己项目，然后是在25年暑假的时候我买少年的源码了，他想让我卖给他我没卖他，之后就没怎么联系了，在25年年低的时候他们在聊天，我就进去了，他说我之前骂他了，我都懵逼了，我不知道我什么时骂他了，之后就这样了，反正我是无所谓，就是感觉他有点忘本，估计是看我赚到钱了之类的（我自己猜的)然后就说要打我频道
Signed 自信
一体底包已测试好，无追封现在，等我加密后发布
Signed 自信
KK 公益直装_V6.0.apk 1️⃣🔤音量键控制悬浮窗 2️⃣🔤大厅出ui ➖➖功能介绍➖➖ 1️⃣🔤KK直装采用裸奔渲染 2️⃣🔤美化采用秒刷美化 3️⃣🔤增加手雷抛物线 ✅更换ios同款绘图 ✅增加内存功能 ✅修复容器闪退 官方频道 @KK666YYDSNB
Signed 自信
Showing the 10 most recent of 10 posts we hold for @KKYYDSNB66. 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.
Citation-graph rank — 362,128 of 1,480,688entries 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.
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.
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.
@KKYYDSNB66 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“KK官方下载频道（新频道）” (@KKYYDSNB66), 563 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/KKYYDSNB66.
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.