Channel
@wechatfeeds
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
16subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001275739447 |
|---|---|
| Type | Channel |
| Username | @wechatfeeds |
| Description | 热门微信公众号精选 https://t.me/topwechat 微信公众号订阅 https://t.me/wechatfeeds 微信WeChat_Feeds https://t.me/WeChat_Feeds 世界新闻 World News https://t.me/media_rss 微博新闻，記錄中國 https://t.me/weibonews |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/wechatfeeds |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 22:02 | 16 | no change |
| 7 Aug 2026, 03:09 | 16 | first reading |
20 posts held, back to 20 September 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 24 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
🚀 Need a temporary email? Use MailsDrop — disposable email addresses directly inside Telegram. Create an email in one tap, receive messages instantly, and use it for: ✅ Signups ✅ Email verification ✅ Testing ✅ Privacy protection No registration. No password. Just open and use. 🌐 Website: https://mailsdrop.com 🤖 Bot: @mailsdropbot 👇 Open the Mini App and get your temporary email now.
🎉 Welcome to One Lotto! 💫 Try your luck and win the jackpot with Telegram Stars! 🎟️ Buy a ticket — simple, fun, and full of surprises. 👇 Tap the button below to start playing!
Want to save money on AliExpress? We share daily deals, promo codes, and coupons you won’t want to miss! Join our channel and grab the best offers before they’re gone! 🔻 Click the button and join 👇
精灵宝可梦（Pokémon）中有哪些有趣的冷（小）知识？ via 知乎每日精选 (author: Tinyu Young)
为什么即时战略游戏越来越落寞？ via 知乎每日精选 (author: 轻声低语)
@小虾汉斯 ｜ @星星伴地球 ｜ @心理学徒李二狗 ｜ @杨角风发作 ｜ @亚亚 ｜ @野树长生 ｜ @壹哥 ｜ @毅种循环 ｜ @泳乐伴读 ｜ @有木聊科技 ｜ @职业规划师燕麦 当然，除了以上「优秀答主」之外，我们也非常感谢每一位充满好奇、热爱分享的知友，期待更多小伙伴们能够开动脑筋，激发小宇宙，也许下一个「优秀答主」就是你。 评选规则及 FAQ 详见： 什么是知乎「优秀答主」标识（原名为「优秀回答者」）？ 来源：知乎 www.zhihu.com 作者：创作者小助手 【知乎日报】千万用户的选择，做朋友圈里的新鲜事分享大牛。 点击下载 via 知乎每日精选 (author: 创作者小助手)
最新一期「优秀答主」名单揭晓，快来看看都有哪些宝藏答主~ ✨ 新一期「优秀答主」今日揭晓，快来点击下方链接，看看他们都是谁吧~ （P.S: 不同话题下的「优秀答主」会按照所属内容领域集中展示哦~） 最新一期「优秀答主」揭晓 再次感谢他们在相关话题下持续创作专业、优质的内容，让知乎的知识星河变得更加璀璨，让无数人从中发现更多开阔眼界的、有帮助的、引发共鸣的内容。 他们分别是（按首字母排名）： @ag獭 | @Arci | @北岸 | @北方车厘子 | @不藏私面包匠人 | @茶茶说道 | @长亭Time | @超哥 | @Chenchen在荒野 | @colaandice | @DBinary | @电车时代 | @丢丢 | @Domino | @独慕溪 | @杜绍斐 DUSHAOFEI | @杜氏利什鳗鱼饭 | @范高 | @凡芒微光 | @Felina | @风飞扬 | @古都闲云 | @宏桑 | @猴姆 ｜ @黄彬彬…
游戏的系列作品，下一作应该如何削弱前作中玩家已经养成的“战神”级角色？ via 知乎每日精选 (author: 无月白熊)
游戏《冰汽时代2》中的“暖券”是什么？在现实中有类似的通货么？ via 知乎每日精选 (author: 段小草)
已经掌握独立建造第三代核电站的技术的国家有哪些？ 谢邀@央视新闻 我是“华龙一号”总设计师邢继。10年之后的我们，可以非常确定地回答题主： 这个名单里，有中国。 这是一道来自2011年11月的提问，就在这道问题提出的8个月前，我们中国自主的百万千万级核电技术的梦想，刚刚被一场发生在日本福岛的核泄漏事故击得粉碎。 那时候，承载了几代核工业人梦想的型号CP1000即将开工，10多台推土机已经抵达现场开始挖土，仅仅3天之后，事故发生，项目被按下了暂停键。 福岛核事故对整个核工业发展的影响非常深远。中国作为一个负责任的大国，在核事故发生5天后，国务院发出声明，针对核安全问题提出四条指导性意见，其中有一条就是 中国未来新建的核电站必须满足国际最高安全标准。 中核集团在第一时间组织专家进行评估后，主动放弃了CP1000，转向全力推进第三代核电技术ACP1000，也就是后来“华龙一号”的自主研发。 放弃“CP1000”，这个决…
Reverse-o1:OpenAI o1原理逆向工程图解 via 知乎每日精选 (author: 张俊林)
你一直坚持热爱的事情是什么？坚持了多久？ via 知乎每日精选 (author: 倪夏莲)
Showing the 12 most recent of 20 posts we hold for @wechatfeeds. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“微信公众号 + Twitter News” (@wechatfeeds), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/wechatfeeds.
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.