🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇

Channel
🍁科技圈 | FQ财报📮
@GFWdaily
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
10,851subscribers
-333 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002042664126 |
|---|---|
| Type | Channel |
| Username | @GFWdaily |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/GFWdaily |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 12:42 | 10,851 | -25 |
| 3 Sept 2026, 15:00 | 10,876 | -11 |
| 2 Sept 2026, 08:44 | 10,887 | -7 |
| 1 Sept 2026, 06:36 | 10,894 | -6 |
| 31 Aug 2026, 10:02 | 10,900 | -10 |
| 30 Aug 2026, 12:24 | 10,910 | -12 |
| 29 Aug 2026, 13:54 | 10,922 | -7 |
| 28 Aug 2026, 13:37 | 10,929 | -11 |
| 27 Aug 2026, 13:37 | 10,940 | -5 |
| 26 Aug 2026, 12:25 | 10,945 | -7 |
| 25 Aug 2026, 11:08 | 10,952 | -18 |
| 24 Aug 2026, 09:28 | 10,970 | -30 |
| 22 Aug 2026, 15:05 | 11,000 | -16 |
| 21 Aug 2026, 05:24 | 11,016 | -9 |
| 20 Aug 2026, 04:25 | 11,025 | -14 |
| 19 Aug 2026, 03:13 | 11,039 | -8 |
| 18 Aug 2026, 00:24 | 11,047 | -14 |
| 16 Aug 2026, 21:27 | 11,061 | -20 |
| 15 Aug 2026, 10:39 | 11,081 | -15 |
| 14 Aug 2026, 02:08 | 11,096 | first reading |
Engagement
68 posts held, back to 26 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 45 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.382%
- avg views ÷ 10,851 subscribers
- Avg views / post
- 41.4
- 49 posts measured
- Reaction rate
- 1.98%
- reactions ÷ views · ER floor
- Posts in window
- 49
- of 68 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 4 of 49 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 68 (26 July 2026 – 1 September 2026) |
| Views total | 2,031 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 19:59 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.
Reaction mix
6 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 33.3% | |
| 😁 | 2 | 33.3% | |
| ❤ | 1 | 16.7% | |
| 🖕 | 1 | 16.7% |
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 6 of the 68 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 26 July 2026 to 1 September 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
TG必备搜索引擎,新币搜 xbso 🔍 中文搜索 @xbso1 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇
英伟达豪掷35亿美元,联发科携手布局“边缘到云”AI\n\n英伟达与联发科宣布深化长期合作,英伟达将认购联发科发行的35亿美元可转债。双方将围绕AI基础设施、本地AI计算和汽车平台展开协作,联发科还将采用英伟达NVLink Fusion,为定制AI加速器接入规模化AI工厂提供路径。\n\n这笔投资的看点不只是资金规模,更在于英伟达正把生态边界从GPU扩展到定制芯片、PC与智能汽车。若合作顺利落地,AI算力的竞争将进一步从单颗芯片,转向芯片互联、封装、软件和整机系统的综合较量。\n\n来源:NVIDIA官方公告\n\n网通社号\n🍁FQ频道 | 📮投稿 | 🍵茶馆\n
英伟达发布 Nemotron 3.5 Lightning:为长期运行的 AI 智能体提速 英伟达近日推出开放模型 Nemotron 3.5 Lightning,采用 30B 混合专家架构,但仅启用 3B 参数,定位是高吞吐、低延迟的智能体“执行层”。它可处理工具调用、结果校验和子任务分派等重复工作,减少每一步都调用大型推理模型带来的延迟与成本。 模型支持 1M 上下文,并提供 BF16 与 NVFP4 版本,兼容英伟达多代 GPU;官方称其在 PinchBench 上以相近准确率比 Qwen3.6 35B 快 30%。权重、训练配方和定制工具已陆续开放,意味着更多开发者可以在本地或私有云部署可控的 AI agent。 来源:英伟达技术博客|The Verge 网通社号 🍁FQ频道 | 📮投稿 | 🍵茶馆
TG必备搜索引擎,新币搜 xbso 🔍 中文搜索 @xbso1 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇
#新闻🍁 AI重新设计抗体,672种分子可进入细胞内 英国艾塞克斯大学团队借助AI重新设计抗体片段,开发出能在人体细胞内部保持稳定的“胞内抗体”。研究称,关键在于调整分子电荷,使其更适应细胞内环境,目标涉及阿尔茨海默症、帕金森病及运动神经元疾病等研究方向。 团队一次改造了672种抗体,针对60种细胞内蛋白质,相关序列在论文发表后开放给其他科学家使用。研究发表于《自然·通讯》,但目前仍属于基础研究,距离临床治疗还需要进一步验证。 科技新报 📌 官方通报 已确认 🕒 时间:2026-08-30 🍁FQ频道 | 📮投稿 | 🍵内部搜索群
#热点🍁 英伟达财报亮眼,AI需求与融资风险同场升温 英伟达公布2027财年第二季度业绩,营收达962亿美元,同比增长106%;数据中心营收同比增长117%,第三季度营收指引上看1080亿美元。财报发布后,股价盘后一度上涨逾4%,市场继续关注AI基础设施扩张速度。 与此同时,公司披露的资料中心相关担保总额最高约1085亿美元,高于单季营收;另有报道指出,记忆体供应可能成为后续增长瓶颈。英伟达管理层仍称AI算力需求正在加速,相关说法引发市场对增长持续性与循环融资风险的讨论。 科技新报 📌 官方通报 已确认 🕒 时间:2026-08-30 🍁FQ频道 | 📮投稿 | 🍵内部搜索群
TG必备搜索引擎,新币搜 xbso 🔍 中文搜索 @xbso1 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇
#热点🍁 人形机器人开始争夺“陪伴”市场 8月23日闭幕的世界机器人大会上,多家公司展示了具备微表情、声音、触觉和情感互动能力的人形机器人。优必选称,其一款仿生人形机器人售价约11.98万至99万元人民币,正式发布前订单量已达13361台。 深圳初创公司Somnia则计划开发身高175厘米、体重20千克的亲密互动机器人,预计2027年中交付。报道指出,AI陪伴正从聊天软件和虚拟角色进入实体设备,但隐私、情感操纵、未成年人保护及监管边界仍引发讨论。 来源:BBC中文 📌 网传信息 / 官方通报:待核实 🕒 时间:2026-08-29 🍁FQ频道 | 📮投稿 | 🍵茶馆
🐴 神马搜索 🔍 👉 精准搜索,极速匹配,给你超高效的搜索体验!快来试试吧! 💡 点击下方按钮快速打开机器人开始搜索 👇
#热点🍁 三星推出1100Hz游戏显示器 三星 8 月 27 日在 Gamescom 2026 公布 2027 年 Odyssey 显示器阵容,其中 27 英寸 Odyssey G6(G60H)主打 FPS 电竞,官方称其为全球首款 1,100Hz 游戏显示器。消息公布后,超高刷新率与实际游戏场景的适配性成为玩家讨论焦点。 这项参数通过“双模式”实现:在 HD 分辨率下最高 1,100Hz,在 QHD 分辨率下最高 600Hz;面板为 Fast IPS、响应时间为 1ms。三星表示该机将于 2026 年下半年全球上市,价格和各地区具体上市时间尚未公布。 网通社号 📌 官方通报 已确认 🕒 时间:2026-08-27 🍁FQ频道 | 📮投稿 | 🍵茶馆
TG必备搜索引擎,新币搜 xbso 🔍 中文搜索 @xbso1 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇
Showing the 12 most recent of 68 posts we hold for @GFWdaily. 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.
Forward network
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.
Mentions
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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“🍁科技圈 | FQ财报📮” (@GFWdaily), 10,851 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/GFWdaily.
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.