Channel
@yunqi
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,107subscribers
-82 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001820895184 |
|---|---|
| Type | Channel |
| Usernames | @leijun @sunnv @tianyou @waigong @wanghui @yunqi |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 68 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/yunqi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 12:21 | 1,107 | -9 |
| 12 Sept 2026, 03:00 | 1,116 | +4 |
| 11 Sept 2026, 18:20 | 1,112 | -5 |
| 11 Sept 2026, 11:16 | 1,117 | -5 |
| 10 Sept 2026, 18:39 | 1,122 | no change |
| 10 Sept 2026, 12:21 | 1,122 | -11 |
| 9 Sept 2026, 12:00 | 1,133 | -4 |
| 8 Sept 2026, 03:39 | 1,137 | -1 |
| 7 Sept 2026, 13:40 | 1,138 | -4 |
| 6 Sept 2026, 07:57 | 1,142 | no change |
| 5 Sept 2026, 17:55 | 1,142 | +1 |
| 5 Sept 2026, 09:37 | 1,141 | -10 |
| 3 Sept 2026, 18:40 | 1,151 | -4 |
| 2 Sept 2026, 22:34 | 1,155 | -3 |
| 2 Sept 2026, 17:55 | 1,158 | +2 |
| 2 Sept 2026, 06:58 | 1,156 | +1 |
| 1 Sept 2026, 17:53 | 1,155 | +1 |
| 1 Sept 2026, 15:57 | 1,154 | -3 |
| 31 Aug 2026, 10:36 | 1,157 | no change |
| 31 Aug 2026, 02:47 | 1,157 | first reading |
12 posts held, back to 30 July 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 6 pages 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
484 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 15.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 75 | 15.5% | |
| ❤ | 73 | 15.1% | |
| 😁 | 72 | 14.9% | |
| 🎉 | 68 | 14.0% | |
| 👍 | 68 | 14.0% | |
| 🔥 | 62 | 12.8% | |
| 🥰 | 62 | 12.8% | |
| 👎 | 2 | 0.413% | |
| 🤡 | 2 | 0.413% |
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 12 of the 12 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 484 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 30 July 2026 to 8 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.
📰 群友投稿｜看电影期间钱包遭恶意多签，150万U被转走 据群友投稿，有用户在不知情的情况下疑似遭遇钱包多签攻击，最终损失约 150万 USDT。 投稿称，相关地址为： TWKgDXLtJYSecoSScKaBGeFWEfrNiiTkWj TLiASw7w7wf7NpVWNuqc5Z6jzpTkTcz6ag 据了解，受害者此前疑似先授权了100多万U，随后另一部手机又授权约44万U，两台设备分别位于中国及东南亚地区。期间用户只是正常看电影，随后发现钱包权限异常，资产被通过多签方式转走。 更离谱的是，事后疑似诈骗方还主动联系并进行嘲讽。 目前上述内容为群友投稿，具体攻击方式及资金流向仍有待进一步核实。提醒大家：涉及钱包签名、授权及多签操作时务必仔细确认权限，避免在不清楚交易内容的情况下随意签名。 #群友投稿 #钱包安全 #多签 #USDT #加密资产 #安全提醒
🎉10😁10🔥7🥰6❤4👍3👏3👎1
📰 TG教程｜A+频道认证流程整理（近期流传版） 近期，圈内流传一份 TG A+ 频道认证操作流程，供有需要的用户参考。 认证步骤： 1️⃣ 联系 @trustchannelbot，接受用户协议。 2️⃣ 阅读认证说明，点击继续。 3️⃣ 分享创建频道所使用的手机号。 4️⃣ 提交需要认证的频道链接。 5️⃣ 将 @trustchannelbot 添加为频道管理员，仅开启添加成员权限。若机器人无响应，可重新发送频道链接。 6️⃣ 输入对应的申请编号，开始验证流程。 7️⃣ 将收到的数字申请编号发送给机器人。 8️⃣ 提交完成后，等待约 10–14 个工作日审核，审核通过后即可获得 A+ 官方认证标识。 提醒： 目前该流程为网络流传版本，是否适用于所有频道、是否一定能够获得认证，仍需以官方实际审核结果为准。 #Tg #A+认证 #频道认证 #TG教程 #Tg频道
👏15❤12🎉11🥰9😁8👍7🔥5👎1
📰 TG技巧｜分享两个最近很实用的 Tg 小技巧 最近不少人在玩这两个 TG 新功能，分享给大家： ① 字体放大排版 发送消息时，先选中文字，点击发送框上方的方形格式按钮，选择 「Aa → 标题」或「标题2」，即可让文字变大，更适合公告、频道内容排版，视觉效果更醒目。 ② 开启 Bot to Bot，拦截 AI 垃圾消息 近期 Tg 为机器人引入了访客模式，部分 Bot 无需进群即可发送消息，一些人开始利用该功能发布垃圾内容。 由于不少群管机器人未开启 Bot to Bot 通信，导致无法接收这些 Bot 消息，也就无法及时删除。 解决方法：进入 @BotFather，找到自己的机器人，开启 Bot to Bot 相关功能，即可让群管机器人接收其他 Bot 消息并及时进行拦截。 #Tg #TG技巧 #BotFather #群管机器人 #AI机器人 #频道运营
🥰13🎉10👏8👍7❤6🔥5😁4
📰 圈内快讯｜云顶PC负责人手机失窃，涉120万U资产，双方已达成和解 据圈内消息，云顶PC股东负责人叶明轩手机日前遗失，随后手机内的USDT、NFT等数字资产被全部转走，连同部分 PC 相关资产也遭到转移，总损失约120万USDT。 据了解，事发期间，相关 NFT ID 曾在凌晨发生两次转移，包括新币交易专群等多个账号权限也受到影响。受事件影响，**公群“N小组22天天PG”**一度暂停运营。 最新消息显示，事件双方已达成和解，相关群组预计将于明日凌晨1点左右恢复正常运营。 #圈内快讯 #云顶PC #数字资产 #USDT #NFT #行业动态
😁10🔥9👏8🥰7👍5❤4🎉2
今日分享TG界四大金刚
👏8❤7😁5👍4🔥3🥰2🎉1
📰 担保圈预警｜顶尖担保资金转出26.4万U，平台风险进一步升级 据链上数据显示，顶尖担保上押地址 TCpu1AsL4v2WeDaw88EoCQgfMDWdquHqcE 于今日向地址 TLyfMiC9gT8LBnwLSb1ssFPbiXjknM5RCU 转出 264,372 USDT。截至发稿，接收地址暂未发现进一步资金异动。 事实上，担保圈此前已连续发布风险提示，关注其负责人长期失联、客服停摆、上下押业务无法正常处理等情况。此次大额资金转移，再次引发市场对平台经营状况的担忧。 据了解，顶尖担保曾长期宣传平台及机器人业务，但业内认为，其盈利模式和运营基础相对薄弱。在当前担保行业整体低迷、市场信任持续下降的背景下，此类平台面临的经营压力更为明显。 需要说明的是，链上资金转移本身并不能单独证明平台已经跑路。但结合长期失联、业务停摆及本次资金异动等多项因素，平台风险已明显升高，建议相关合作方提高警惕，密切关注后续进展，谨慎处理资金往来…
❤9👍7👏7😁5🎉4🔥4🥰1
📰 Tg动态｜Tg 已恢复上架苹果 App Store 今日，Tg 刚刚在 苹果 App Store 出现下架情况，引发大量用户关注。消息传出后，市场情绪短暂波动，TON 价格也一度受到影响。 不过，最新消息显示，Tg 已恢复上架 App Store，官方表示应用将很快重新向所有用户开放下载。 截至目前，Tg 并未说明此次短暂下架的具体原因，事件原因仍然未知。 此次风波持续时间较短，随着应用恢复上架，市场情绪也逐渐趋于稳定。不过，具体是否涉及审核、技术或其他原因，仍需等待官方进一步说明。 PS： 刚刚还在担心“以后怎么上 TG”，结果 Tg 已经火速回来了。😄 #Tg #AppStore #TON #行业动态 #苹果 #TG资讯
😁10👏9👍7❤4🎉4🔥4🥰3
📰 行业快讯｜富贵娱乐疑再遭攻击，应急响应及时未现资金损失 据圈内消息，今日上午9时左右，黑客组织“方阳”在相关群组发布消息，称再次对富贵集团旗下主平台富贵娱乐发起攻击，并疑似突破部分账户余额。 不过，消息称富贵集团安全团队迅速启动应急响应，及时采取处置措施，此次攻击未造成黑客获利。 此次事件再次提醒行业，面对持续升级的网络攻击，平台应不断完善安全防护及应急响应机制，降低潜在安全风险。 #行业快讯 #富贵娱乐 #富贵集团 #网络安全 #黑客攻击 #数据安全
❤9👍7👏5🥰4😁4🎉3🔥3
📰 行业观察｜硬件钱包真的安全吗？供应链风险再引热议 近日，随着 Coldcard 相关事件持续发酵，硬件钱包供应链安全问题再次成为业内讨论焦点。 有业内人士指出，包括 OneKey、Ledger 等品牌在内，部分硬件钱包产品采用第三方代工模式，生产、运输及组装涉及多个环节。若供应链管理不到位，理论上可能增加设备在生产或流通过程中被篡改的风险。 不过，需要说明的是，目前并无公开证据表明 OneKey 或 Ledger 因代工生产而存在已证实的供应链安全问题。相关观点更多属于业内对供应链安全的讨论，而非对具体产品安全性的定论。 业内建议，购买硬件钱包时应尽量通过官方渠道，收到设备后检查包装完整性，并严格按照官方流程初始化和验证设备，避免使用来源不明或已拆封的产品。 #硬件钱包 #Coldcard #OneKey #Ledger #供应链安全 #加密货币 #行业观察
🎉7🔥5😁5🥰4❤3👍3👏3
📰 行业快讯｜巨富娱乐疑遭黑客方阳入侵，会员数据传遭出售 据圈内消息，富贵娱乐旗下「巨富娱乐」疑似遭遇黑客攻击，平台会员数据据称已被获取，并在相关渠道流传出售。 消息称，此次事件涉及资金约 14 万 USDT，平台后续成功拦截追回约 5 万 USDT，目前预估损失约 9 万 USDT。 截至发稿，相关平台尚未就事件发布正式公告，会员数据是否被泄露、出售范围及具体损失情况仍有待进一步核实。 此次事件再次提醒行业，平台应持续加强网络安全防护、数据权限管理及风险监测，降低数据泄露和资金损失风险。 #行业快讯 #巨富娱乐 #富贵娱乐 #数据泄露 #黑客方阳 #网络安全
❤8🎉7👍7🔥6👏3🥰2😁1
🎉 7月最后一天｜这个月，你赚了多少？ 有人收获满满，有人还在寻找机会。 新的一个月即将开始，愿8月抓住风口、抓住机会，业绩一路长虹，月入百万 USDT！ 💰🚀 持续关注 《痴情的发财日记》，每日分享 TG大事件、行业动态、项目实操、发财机会，一起见证更多机会。 📍 频道：@yunqi（运气全拼） 📍 个人：@chiqing（痴情全拼） #发财日记 #8月暴富 #TG资讯 #行业动态 #项目分享 #月入百万USDT
👍10🔥6😁6❤4🥰4🎉3
📰 网友投稿｜福利来红包外挂“翻车”，自动报名游戏反赔5000元 近日，有网友投稿称，一名用户因开启自动抢红包外挂，意外触发钱包活动，最终不仅没赚到钱，反而损失约5000元。 据爆料，该外挂可在数百毫秒内自动识别并点击“参加”按钮。当某钱包上线随机领红包及**骰子「炸金花」**活动后，外挂误将活动识别为红包，自动完成报名，而玩家本人当时并未在线。 由于游戏规则要求45秒内完成摇骰子操作，超时即判负。结果外挂替用户报名后无人操作，连续多局被系统判定失败，最终造成约5000元损失。 事件引发圈内热议。有网友调侃：“外挂抢红包确实快，结果最后坑的还是自己。” 提醒大家，以上内容为网友投稿，使用外挂不仅可能违反平台规则，也可能因误操作带来意外损失，得不偿失。 #网友投稿 #红包外挂 #抢红包 #翻车事件 #行业吃瓜
🥰7🎉6👏6🔥5😁4❤3👍1
Showing the 12 most recent of 12 posts we hold for @yunqi. 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.
Named by 10 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“痴情的💎发财日记💎@Yunqi” (@yunqi), 1,107 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/yunqi.
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.