UI
Signed WANYO(XERO TEAMWORK)

Channel
@laoliufx
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001867386012 |
|---|---|
| Type | Channel |
| Username | @laoliufx |
| Created | Between 1 October 2022 and 24 November 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/laoliufx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 22:17 | 6 | -1 |
| 22 Aug 2026, 18:34 | 7 | -1 |
| 12 Aug 2026, 14:34 | 8 | no change |
| 7 Aug 2026, 08:18 | 8 | first reading |
15 posts held, back to 24 November 2022 — 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 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 15 posts for this entry, the most recent from 5 December 2022. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
UI
Signed WANYO(XERO TEAMWORK)
互管 频道 https://t.me/laoliuyyds 联系 @PUBGlaoliu
Signed 老六 (XERO 团队 🇨🇳)
内部提卡链接 呆呆内部马上面临涨价 欢迎各位加入 http://g3v.cn/3epWK3
Signed 老六 (XERO 团队 🇨🇳)
内部提卡链接 http://g3v.cn/3epWK3
Signed 老六 (XERO 团队 🇨🇳)
高中少女原片😍😍😍 点我查看:https://t.me/Madoucm_bot?start=30l3bi
Signed 万叶(XERO团队🇨🇳)
第一次引流可删,别下管
Signed 虽然来了
超过两百人送超凡先锋毒液卡密
Signed 虽然来了
教学由XERO团队制作: 卡密验证区: 对接T3 对接易游 修改器区: 修改器教学(必学)7 旁路转脚本 旁路转成脚本的模板 抓脚本旁路的工具(必用) 直装: 迅游加速器破解版 aide和ndk(工具)1 NDK导入AIDE(必用)2 汉化文件(汉化必用) 二改直装(改名字什么的)3 汉化直装(汉化)5 打包(新手必看)4 直装全系统 改全系统的软件 main加防封 上面是新手区 源码里面没有旁路事件的加法 (适用于没有旁路的源码) main改ui教学 加功能 关于过签包6 2.2转2.3(源码 国际服同理) 虚拟机导入obb 端口: ADG全局离线和规则 工具 防封: 防10 防禁网防追封 思路和工具 CD防追封 科普视频(你关于防的大部分问题都在这) 虚拟机 修改器 虚拟机需要有面具全家套 虚拟机8 修改器9 加入频道 10! 搬运请带频道谢谢! 视频也是一样的 发平台记得带电报,不然全…
Signed 万叶(XERO团队🇨🇳)
XERO🇨🇳 内部已更新 XERO老六频道 https://t.me/laoliuyyds XERO团队频道 https://t.me/wanxero XERO老六思慕内部提卡 现在25一人 http://g3v.cn/2upMm0 ------------------------- XERO🇨🇳 XERO Sixth Sniper Channel https://t.me/laoliuyyds XERO team Channel https://t.me/wanxero XERO old six Simo internal Tika At present, 25RMB for one person http://g3v.cn/2upMm0
Signed 老六 (XERO 团队 🇨🇳)
Video, posted without a caption
Signed 老六 (XERO 团队 🇨🇳)
明日全防食用协议 1.不要拉闸了就狗叫 自己找原因 诽谤 人身攻击者拉黑 2.我不是有钱人不能一直维持公益后面会进行半收费 3.出现任何问题不要鸡脚 联系 @lmhlj 解决 4.发了没反馈嘶全+ 5.内防只是帮助腾讯找到漏洞并且修复基址全防 没有触碰腾讯任何人的利益 6.可能会被同行顶上 请你们像ikun一样不惹事也别怕事 目前版本1.0 执行码10839 反馈联系 @lmhlj 加入 @wanxero
Signed 万叶(XERO团队🇨🇳)
XERO🇨🇳 XERO老六频道 https://t.me/laoliuyyds XERO团队频道 https://t.me/wanxero XERO老六思慕内部提卡 现在25一人 http://g3v.cn/2upMm0 ------------------------- XERO🇨🇳 XERO Sixth Sniper Channel https://t.me/laoliuyyds XERO team Channel https://t.me/wanxero XERO old six Simo internal Tika At present, 25RMB for one person http://g3v.cn/2upMm0
Signed 老六 (XERO 团队 🇨🇳)
Showing the 12 most recent of 15 posts we hold for @laoliufx. 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.
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.
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.
@laoliufx named 3 handles 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“科技模块公益分享(XERO 团队 🇨🇳)” (@laoliufx), 6 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/laoliufx.
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.