Telegram RegisterThe public register of Telegram
Telegram profile photo for Xiao Mi Core

Channel

Xiao Mi Core

@XiaoMiCore6

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

1,334subscribers

-9 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1002843387713
TypeChannel
Username@XiaoMiCore6
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/XiaoMiCore6

Growth

1,3341,3431,338.520 August 2026 — 1,343 subscribers21 August 2026 — 1,342 subscribers24 August 2026 — 1,339 subscribers28 August 2026 — 1,336 subscribers30 August 2026 — 1,334 subscribers20 August 202630 August 2026
5 measurements spanning 10 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 1,333–1,344 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 22:141,334-2
28 Aug 2026, 03:021,336-3
24 Aug 2026, 18:531,339-3
21 Aug 2026, 10:581,342-1
20 Aug 2026, 18:451,343first reading

Engagement

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

ERR · 30 days
7.41%
avg views ÷ 1,334 subscribers
Avg views / post
98.8
5 posts measured
Reaction rate
4.81%
reactions ÷ views · ER floor
Posts in window
5
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. It is computed over the 2 of 5 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 20 August 2026
Posts held20 (19 May 202620 August 2026)
Views total494
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 18:45 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
29s
Average length
29s

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

8 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍562.5%
337.5%

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 4 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 8reactions 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 19 May 2026 to 20 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

20 Aug 2026, 16:45 UTC12 views2 reactionsread 20 August 2026

KH 内核项目 imgui自写项目 模式如下: 普通模式:单透模式 单内核级陀螺仪模式 追踪模式:单追模式 追锁模式 内部功能: 全新UI 模型露打 掩体变色 完美骨骼 手持文字和图片枪械绘制 陀螺仪自瞄 : 多种调节与无目标压枪 断点追踪:权重追踪 框内追踪 指哪打哪 多种调节 解密:使用的纯人物数组解密 道听途说一百遍 不如亲身试一遍 有什么问题可以找群主或者@LQXZzzBot 下载链接: https://pan.quark.cn/s/8be7a6ab6161

👍2

Signed 0v0

15 Aug 2026, 14:01 UTC92 views3 reactionsread 20 August 2026
Forwarded from @KH0v0Video

无目标压枪

👍3

Signed 挽柯

7 Aug 2026, 18:19 UTC177 viewsread 20 August 2026
Forwarded from @DxCheatCN

DX团队培养一批独家流量主播有工资认为自己可以胜任的直接来报名!审核要求不高,重要的是保持一颗赤诚的心!有肉大家一起吃有汤大家一起喝,合家欢乐! 感觉自己可以就来联系客服审核+群带个人社交主页哦 @DXkf996

Signed JOJO

5 Aug 2026, 19:04 UTC120 viewsread 20 August 2026
Forwarded from @DxCheatCNPhoto

🤩高端一体直装🇨🇳 高速下载网盘: https://share.feijipan.com/s/zs64ku2y 🤩战神,王牌,巅峰赛,地铁英雄传奇反馈图转图频道 @DXfk66 🤩点我一键扫码加入QQ聊天群 🤩唯一正版频道 @DXCheatCN 语言支持:中文,英语,阿拉伯语 共同ESP内容:人物,物品,车辆 装载机追踪版本:部位概率子弹追踪,防录屏,十字架,iPad视角,安卓10+通用支持 一体直装自瞄版本:漏打自瞄,皮肤美化,击杀播报美化,基础功能,iPad视角 反馈发送 @DXkf996 🤩 DX cheat 创作者百万扶持计划 💯发作品/开直播 达标即领💰 无门槛 😮作品/直播内容: 测评类 击杀秀 等 🖥作品奖励(新作品结旧作品当日一次) 10-30赞 10+赞=2.88元 30-80赞 30+赞=6.88元 80-150赞 80+赞=10.88元 150+赞 根据数量按比例结算(越多越高)

Signed JOJO

5 Aug 2026, 18:22 UTC93 viewsread 20 August 2026
Forwarded from @DxCheatCNPhoto

🤩高端一体直装🇨🇳 高速下载网盘: https://share.feijipan.com/s/zs64ku2y 🤩战神,王牌,巅峰赛,地铁英雄传奇反馈图转图频道 @DXfk66 🤩本月公益卡密:JOJO>30D-u7tRb 语言支持:中文,英语,阿拉伯语 共同ESP内容:人物,物品,车辆 装载机追踪版本:部位概率子弹追踪,防录屏,十字架,iPad视角,安卓10+通用支持 一体直装自瞄版本:漏打自瞄,皮肤美化,击杀播报美化,基础功能,iPad视角 反馈发送 @DXkf996 🤩 DX cheat 创作者百万扶持计划 💯发作品/开直播 达标即领💰 无门槛 😮作品/直播内容: 测评类 击杀秀 等 🖥作品奖励(新作品结旧作品当日一次) 10-30赞 10+赞=2.88元 30-80赞 30+赞=6.88元 80-150赞 80+赞=10.88元 150+赞 根据数量按比例结算(越多越高) 连续3个作品超过200赞

Signed JOJO

10 Jul 2026, 14:21 UTC291 viewsread 20 August 2026
Forwarded from @DevilcheatCNFile

📢 DEVIL 应用全新更新,现已支持 4.5 赛季 🚀 💥 亲爱的用户: 您现在可以更新游戏,体验 4.5 赛季 的全部新功能。 ✅ 更新方法: 📲 请直接将新版本安装覆盖旧版本,无需卸载当前版本。 ❤️ 感谢您一直以来的信任与支持! #DEVIL中国团队 ━━━━━━━━━━━━━━━━━━━ 📢 New DEVIL App Update – Now Supporting Season 4.5 🚀 💥 Dear Subscribers, You can now update the game and enjoy all the new features of Season 4.5. ✅ Update Instructions: 📲 Simply install the new version over the old one. There is no need to uninstall the previous versio

Signed JOJO

10 Jul 2026, 12:38 UTC232 viewsread 20 August 2026

最近和小悠商讨回归,其实我已经在用空闲时间写了

Signed 小宝

24 Jun 2026, 08:15 UTC390 viewsread 20 August 2026
Forwarded from @DevilcheatCNFile

①修复帧率异常问题 ②更换人物解密方案 人物绘制 触摸瞄准 概率追踪 安全功能 安全模式 坐标解密 本产品首次运营在24年如今我们团队依然保持初心回归运营给大家带来安全稳定的作弊器。 客服 @Memeetop1 反馈 @jyfkbot CN中国唯一正版频道 @DevilcheatCN 猫猫の卡密小卖部:https://shop.ymy9.com/shop/MMD 猫猫の极品八级号:https://shop.zmfaka.cn/shop/MMD 恶魔插件使用教程点一下哦 恶魔插件下载地址点一下哦 欢迎各位宝宝对接猫猫的卡网 注册链接: https://shop.ymy9.com/merchant/dashboard 猫猫的专属对接码:Memeetop1

Signed JOJO

8 Jun 2026, 15:06 UTC454 viewsread 20 August 2026
Sticker

Sticker, posted without a caption

Signed 多事之秋

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

Citation-graph rank — 1,129,030 of 1,628,524entries 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.

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.

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

“Xiao Mi Core” (@XiaoMiCore6), 1,334 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/XiaoMiCore6.

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.