Channel
@fengryz
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
87subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002370614313 |
|---|---|
| Type | Channel |
| Username | @fengryz |
| Description | 专注 UX / 交互设计线上课程、专业文献与全球设计师社群的垂直设计教育平台 Telegram最全RSS自动推送，一键订阅全网热点: @TGRSS |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fengryz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 15:46 | 87 | no change |
| 6 Aug 2026, 19:52 | 87 | first reading |
20 posts held, back to 22 June 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (22 June 2026 – 9 August 2026) |
| Views total | 145 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 15:46 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.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
来自速搜推荐 @SSOU 📢今天也想尖叫🐱 📢利博百家乐 百家乐代理 ... 📢国际足球联赛世界杯冠军会... 📢欧博私网 亚星私网 欧博... 📢换妻 绿帽优选 📢叁友科技|源头数据【诚信... 📢线上博彩--开云棋牌-体... 📢欧博私网 欧博会员 亚星... 📢南宫集团-壹号国际-PG... 📢999 理赔/曝光群 📢🔞 反差丨绿婊丨母狗丨... 📢热门游戏|经典|吃鸡|D... 📢明星 换脸 泄露 📢新京报 📢国产AV 麻豆糖心 福利... 👉流量互推规则介绍💥 以下是广告推荐 📢 Ton 中文索引 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 📢💹567U时代火爆上线！招收玩家/代理，匿名开户，放心娱乐！ 📢💎 【8.cc】U投领导者 千万域名 百亿大盘 充值笔笔加赠3% 📢 飞驰号铺 [主营：飞机号 开会员 代充星星] 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelp…
❤️欢迎来到 TGRSS —— Telegram 上最智能、最全能的 RSS 自动内容矩阵！ 在这里，你不需要手动刷新网页、不需要下载 App、不需要错过任何热点。 TGRSS 通过实时 RSS 订阅 + 自动化推送，为你打造了一个“内容永不缺席”的私人信息流： 实时全球新闻：科技、财经、国际大事，一秒不落 成人专区（18+）：精选故事、幽默、亲密建议与行业动态（纯链接推送，安全隐私优先） [❤️🔥赞助商]TGFOX矩阵机器人 👩🏻⚕️广告投放： @TGRSS123 🚀支持200+频道同时投放，所有频道每天推送一次
夏季特别优惠：加入 IxDF 并获得 10 门免费大师课程，价值 500 美元 今年夏天，IxDF 让您有机会免费向 10 位行业专家和设计领袖学习！仅限 8 月份，新会员即可获得 10 场免费大师班 @ixdf_org | ixdf.org • Aug 1, 2026
巅峰体验设计 旨在满足每个人的产品不足以创造难忘的体验。峰值体验的概念强调了专门针对目标受众进行设计的重要性。 William Hudson | ixdf.org • Jul 24, 2026
如何创建研究支持的用户角色：UX 设计师 2026 年指南 通过我们的 2025 年用户体验指南掌握角色——通过真实的研究进行构建，调整团队，并让您的设计职业面向未来。 @ixdf_org | ixdf.org • Jul 18, 2026
找到这份工作：顶级设计领导者真正在投资组合中寻找什么 设计专家揭示了他们制作一个让你获得面试机会的作品集的秘诀。了解行业领导者的重要见解。 Laia Tremosa | ixdf.org • Jul 18, 2026
尝试不同的角色来解决你的问题——爱德华·德博诺的六顶思考帽 爱德华·德·博诺的六顶思考帽方法鼓励你尝试不同的角色，以看到解决问题和创造力的新视角。观看此视频了解更多信息！ @ixdf_org | ixdf.org • Jul 17, 2026
保密：如何展示您受 NDA 保护的设计作品 了解如何在尊重机密性的同时建立强大的投资组合。设计总监 Morgane Peng 分享专家建议。 Laia Tremosa | ixdf.org • Jul 17, 2026
如何增强自己的创造力 人们常常以你永远不会对待他们的用户（或其他任何人）的方式对待自己。了解如何在给定“你是谁”的情况下成功并实现你的目标，而不是试图改变你是谁。 @ixdf_org | ixdf.org • Jul 16, 2026
如何在短期时间管理计划中利用待办事项列表的力量 待办事项清单是否困扰着您，不断提醒您尚未完成的事情？好吧，那就扭转局面吧！重新想象待办事项列表，帮助您清理心理空间并庆祝成就 @ixdf_org | ixdf.org • Jul 11, 2026
糟糕想法有什么好处？ 你可能仍然会想，为什么花宝贵的时间去思考坏主意是一个好主意？在这个视频中，你将了解到三个主要原因解释为什么... @ixdf_org | ixdf.org • Jul 4, 2026
用户体验中的认知地图 | IxDF 了解UX中的认知地图如何帮助设计师理解用户的心理模型。探索它们的类型、好处以及相关的访谈过程。 Mads Soegaard | ixdf.org • Jul 3, 2026
Showing the 12 most recent of 20 posts we hold for @fengryz. 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 — 609,034 of 1,160,990entries 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.
Named by 24 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“IxDF 交互设计” (@fengryz), 87 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/fengryz.
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.