Telegram RegisterThe public register of Telegram
Telegram profile photo for YuKongA | Channel

Channel

YuKongA | Channel

@YuKongA13579

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

6,939subscribers

+394 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001376694766
TypeChannel
Username@YuKongA13579
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/YuKongA13579

Growth

6,5456,9396,7426 August 2026 — 6,545 subscribers6 August 2026 — 6,562 subscribers9 August 2026 — 6,667 subscribers12 August 2026 — 6,788 subscribers16 August 2026 — 6,939 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net +394. 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 6,486–6,998 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 07:046,939+151
12 Aug 2026, 13:256,788+121
9 Aug 2026, 22:316,667+105
6 Aug 2026, 22:356,562+17
6 Aug 2026, 07:316,545first reading

Engagement

27 posts held, back to 24 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 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
48.6%
avg views ÷ 6,939 subscribers
Avg views / post
3,370
27 posts measured
Reaction rate
1.14%
reactions ÷ views · ER floor
Posts in window
27
of 27 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. It is computed over the 25 of 27 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held27 (24 July 202611 August 2026)
Views total91,090
Reactions total969
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:54 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
18s
Average length
9s

Measured directly from 2 videos 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

871 reactions across 21 posts, in 22 distinct kinds. The most used accounts for 37.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
32437.2%
🔥13315.3%
👍11012.6%
🥰9310.7%
🤯465.28%
🌭283.21%
🤩232.64%
😁212.41%
🤔182.07%
👾171.95%
👌131.49%
🤣101.15%
🤮80.918%
🫡60.689%
🐳50.574%
😘40.459%
30.344%
🏆30.344%
💯20.23%
🤡20.23%
2 further kinds20.23%

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

Measured over the 27 most recent posts we hold, published 24 July 2026 to 11 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.

Telegram Stars

Stars received
22
across the posts below
Posts paid on
7
of 27 we hold a reading for · 26%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @YuKongA13579. 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 27 most recent posts we hold for this entry, published 24 July 2026 to 11 August 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

11 Aug 2026, 16:34 UTC≈1,010 views65 reactionsread 12 August 2026

首先,我不是免费苦力!我虽然一般比较好说话,但也不是上来就给我一句适配一下这个的理由。 如果你是 6.6 或 6.12,当前项目的脚本已经非常可靠,你可以自己通过脚本检查内核是否受支持并生成偏移值。基本上只要脚本检查通过,能够生成偏移值,那就都是可行的。对于这类受支持内核,你找我弄倒是也没什么难点,但我也没这么闲。 那如果你不是 6.6 和 6.12,目前软件提供的代码实现均不支持,我也没有引入其他的可用利用链,比如 umh 和 mcast 这些。目前市面上这些已有的方案能跑通多数 5.10/5.15/6.1 内核,但我的设备都用不上,因此你也不用尝试使用脚本生成。 如果你愿意把这两条或者其他新利用链 pr 给我,那我举双手欢迎。不过部分利用链无法实现免 uid2000 完成,你可能仍然需要 shizuku,或者还需要做不少工作。我本人只有 6.6 的 oppo find n5 和 6.12 的小米 17 pm / 一加

60👍3😘2

9 Aug 2026, 03:16 UTC≈2,900 views49 reactionsread 12 August 2026
File

GhostLock 一键 ROOT 更新 260809: - 添加了更多受支持的内核,详见评论 - 支持选择 CPU 组,大核理论快一些 - 添加对 ReSukiSU 的支持,未实测 注意事项: - 理论上可以支持能利用 CVE-2026-43499 的所有内核,欢迎 PR - 执行前请先自行安装 KernelSU/ReSukiSU 管理器,以正确调用 ksud - 由于漏洞性质,卡死和失败是很正常的,可能需要尝试多次才能成功 GitHub:https://github.com/YuKongA/ghostlock-app #ghostlock #misc

🔥395👍5

7 Aug 2026, 08:19 UTC≈3,220 views27 reactionsread 12 August 2026

咱来说说: https://api.huanji.comm.miui.com/ota-guide/home?device=popsicle&language=zh_CN&osVersion=OS3.0&performanceLevel=HIGH&sku=&type=PHONE&cnFlag=cn&showPages=&currentPageId=local_welcome_page_key&isOuter=0&isFirstBoot=true 以上链接是 os3,那 os4 是什么呢...? 但这样还不是 os4 风格,问题出在 index.html,只提示到这了 #hyperos #misc

🤯23🤣4

7 Aug 2026, 07:41 UTC≈3,130 views26 reactionsread 12 August 2026
File

GhostLock 一键 ROOT 更新 260807: - 添加了更多设备,详见评论 注意事项: - 执行前请先自行安装 KernelSU 管理器,以正确调用 ksud - 理论上可以支持能利用 CVE-2026-43499 的所有内核,欢迎 PR - 由于漏洞性质,卡死和失败是很正常的,可能需要尝试多次才能成功 GitHub:https://github.com/YuKongA/ghostlock-app #ghostlock #misc

👾17🫡63

6 Aug 2026, 14:28 UTC≈3,070 views69 reactions2 Starsread 12 August 2026

刚刚酷安看了一圈,一堆需要 shizuku 的所谓 “一键” 提权软件在圈钱,我是不是不应该开源😳 #misc

47😁20🤡2

6 Aug 2026, 13:56 UTC≈3,210 views41 reactionsread 12 August 2026
Photo

GhostLock 一键 ROOT 目前只支持图中内核版本,具体适用设备非绑定,支持情况以内核为准 如 Xiaomi 17 系列都是 6.12.23-android16-5-g75e9b1c7ae7c-abogki463945075-4k,所以是通用的 理论可以支持能利用 CVE-2026-43499 的所有内核,欢迎 PR 执行前请先安装 KernelSU 管理器。此外,由于该漏洞需要堆喷射,卡死或者失败是很正常的 GitHub:https://github.com/YuKongA/ghostlock-app #ghostlock #misc

🔥29🤯65🥰1

5 Aug 2026, 12:17 UTC≈2,900 views54 reactionsread 12 August 2026
Video

也是能一键 root 了 已提交:https://github.com/YuKongA/ghostlock-oplus/commit/3181e7128df5979b962b9eaff43e179fcdd4f0b1 目前支持 oppo find n5 / find x8 的 6.6.118 版本 #oppo #misc

🥰493😘2

3 Aug 2026, 13:45 UTC≈3,460 views56 reactions5 Starsread 12 August 2026
File

🤨 小米 17 系列 TWRP-16 3.7.1 B2 🤨 # 更新日志 ## 速度 - 开机到解密页 17.4s → 3.3s - 输密码到主界面 6.0s → 1.5s ## 修复 - 修复三处空指针崩溃 - 备份分卷上限 99 → 999 - 卸载 /data 后不再谎报已解密 - 备份取消或失败时清理残留目录 - 取消备份不再被报成"备份完成" ## 界面 - 去掉空槽位造成的 "Storage (0MB)" 条目 - 可移动存储优先显示卷标,重名时补编号 - 重启项 Fastboot 更名 Fastbootd 并排到 Bootloader 之上 - Super 条目显示分区数量,不再列举分区名撑爆行宽 支持设备: Xiaomi 17 Xiaomi 17 Pro Xiaomi 17 Pro Max Xiaomi 17 Ultra 主要测试设备: Xiaomi 17 Pro Max,我自己只有该设备,上方数据也

🥰31👍205

3 Aug 2026, 10:49 UTC≈2,750 views41 reactionsread 12 August 2026
Video

下版本给启动和解密流程做一下优化🤪 理论上应该会快非常非常非常非常多😆 #twrp

🔥343💯21😁1

3 Aug 2026, 03:03 UTC≈3,240 views58 reactions8 Starsread 12 August 2026
File

🤨小米 17 系列 TWRP-16 3.7.1 Beta-1🤨 - 首个公开 Beta 版本 相比上个测试版本: - 内置 7za 和 zstd - 优化 各服务的启动时序 - 修复 震动 prop 设定 - 修复 otg 相关的异常问题 - 修复 apex 相关的红字报错 - 修复 17 Pro Max 震动不工作 支持设备: Xiaomi 17 Xiaomi 17 Pro Xiaomi 17 Pro Max Xiaomi 17 Ultra 主要测试设备: Xiaomi 17 Pro Max,毕竟我自己只有这台 可选捐赠: 爱发电 GitHub: https://github.com/YuKongA/twrp_device_xiaomi_sm8850 #TWRP

51🌭4❤‍🔥1👍1🥰1

2 Aug 2026, 13:52 UTC≈2,890 views53 reactions1 Starread 12 August 2026

提醒一下,我放生了我的 id,现在包括 yukong、yukonga 等任何类似相关的 id 都不是我,不要被骗!! #misc

35👌13🐳5

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

Posts edited after publishing

@YuKongA13579 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
10 August 2026

Citation-graph rank

Citation-graph rank — 89,896 of 1,480,975entries 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

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.

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

“YuKongA | Channel” (@YuKongA13579), 6,939 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/YuKongA13579.

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.