Telegram RegisterThe public register of Telegram

Channel

Fᴜғᴜ の Cʜᴀɴɴᴇʟ

@i_chl

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

764subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002272312208
TypeChannel
Username@i_chl
Description群组 👉 @i_grp 拿来当做收藏夹用的 代码问题一问三不知
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/i_chl

Growth

764765764.57 Aug 2026, 13:49 — 765 subscribers7 Aug 2026, 23:28 — 764 subscribers8 Aug 2026, 01:50 — 764 subscribers7 Aug 2026, 13:498 Aug 2026, 01:50
3 measurements taken within a single day, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 764–765 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:50764no change
7 Aug 2026, 23:28764-1
7 Aug 2026, 13:49765first reading

Engagement

19 posts held, back to 24 June 2026the 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 · 30 days
37.6%
avg views ÷ 764 subscribers
Avg views / post
287
4 posts measured
Reaction rate
0.298%
reactions ÷ views · ER floor
Posts in window
5
of 19 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 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held19 (24 June 202629 July 2026)
Views total1,149
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:50 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.

What this channel posts

Photos
77
Links
200

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

6 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤯466.7%
custom 5044162351524217754116.7%
116.7%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 19 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 24 June 2026 to 29 July 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

28 Jul 2026, 05:54 UTC245 viewsread 8 August 2026

▎OpenAI 查询 OpenAI 帐户真实关联的电话号码 该号码适用于 Codex 验证且一经绑定无法修改 Platform 该入口被隐藏或移除,直达链接 https://platform.openai.com/settings/profile/user 账户安全与登录 中的 Text message 仅仅是作为 ChatGPT 登录验证方式,并非 OpenAI 帐户真实关联的电话号码 补充:最新版的 ChatGPT App 就可以看到真实关联的电话号码,但是主包 iOS16.6 系统版本过低 ChatGPT App 许多功能都没有所以看不了,没关注到这个点 #OpenAI #ChatGPT #Codex #Tips

18 Jul 2026, 20:02 UTC344 viewsread 8 August 2026

▎ChatGPT Business 车已开走,评论区招租! UK Team 双席位 GB£36 GB£11/Month 48 个月优惠,立减 GB£25 https://chatgpt.com/?promoCode=ramsacuk 提取长链支付 (async function generateAUTeamLink() { // ================= 配置项 ================= const WORKSPACE_NAME = "xxx"; // 优惠码 const COUPON = "ramsacuk" const SEAT_QUANTITY = 2; // 席位数量(Team 最少 2 个) // ========================================== console.log("⏳ 正在获取 ChatG

16 Jul 2026, 03:59 UTC336 views1 reactionsread 8 August 2026
Photo

▎Telegram Premium ⭐ CN¥199 上号代开 Telegram Premium 年费! 联系:@oifufu / @i_pm_bot 美区正价 US$35.99 ≈ CN¥243.95 注: - 注意是上号代开!介意的就不用联系了!数量有限! #TG #Telegram #Premium #电报 #大会员 #羊毛

custom 50441623515242177541

12 Jul 2026, 04:25 UTC602 viewsread 8 August 2026
Photo

▎ChatGPT(Codex) 利好 CPA 反代 利好中转站反代(👀 Via:X/Tibo #ChatGPT #Codex #CPA #CLIProxyAPI #Sub2API #中转站

12 Jul 2026, 03:30 UTC415 viewsread 8 August 2026

▎Open Minis 一款超越对话框的设备端 AI 智能体。它能自主行动——浏览网页、读取健康数据、管理日程、控制智能家居、自动化复杂任务。一切都在你的设备上私密完成。支持 iOS、Android、macOS 和 visionOS 项目官网 https://openminis.app 项目地址 https://github.com/OpenMinis/OpenMinis 算是移动端对接中转站非常不错的三方 App 了👏 iOS 平台上用了很久了,昨天发现上了 Android 平台🤩 #OpenMinis #Minis #Recs #中转站

10 Jul 2026, 11:00 UTC514 views0 reactionsread 8 August 2026

#互推 【资源分享】小声逼逼 【安卓黄游】安卓黄油の领域(转世重生ver)❤️ 【网络分享】Appinn Feed|小众软件 【软件分享】iOS破解游戏软件分享 【音声&涩涩】永不消逝的音声 【科技分享】Fᴜғᴜ の Cʜᴀɴɴᴇʟ 【资源分享】资源分享客栈-Applnn 【壁纸美图】一个普通的壁纸频道喵~ 【机场测评】小众机场测评 Powered by @Summer_Clear_Sky_Bot

9 Jul 2026, 13:56 UTC434 viewsread 8 August 2026
Forwarded from @JsforbabyFile

GitHub源文件自动CDN = type=http-request, pattern=^https?://raw\.githubusercontent\.com/.+, script-path=index.js, timeout=5 将 raw.githubusercontent.com 的请求自动重定向到 jsDelivr CDN,解决 GitHub Raw 访问缓慢或无法连接的问题。 好像可以解决最近GitHub429的问题 私有仓库(gist链接)的文件无法通过 jsDelivr CDN 访问 用的是 这个模块 (打不开就看脚本文件) https://raw.githubusercontent.com/Yuheng0101/X/main/Scripts/GitRawAutoCDN/surge.sgmodule 项目介绍: https://github.com/Yuheng0101/X/blob/main/Scrip

9 Jul 2026, 13:18 UTC416 viewsread 8 August 2026
Forwarded from @zhetengshaPhoto

optimizerDuck: 免费开源的 Windows 性能优化与隐私控制工具 感谢群友 @suye_nyx 分享 • 提供 30+ 项 Windows 系统优化,覆盖性能、隐私、显卡、电源、服务和使用体验 • 内置启动项管理、计划任务、磁盘清理、预装软件卸载和系统面板 • 支持本地备份、一键还原和风险分级,适合谨慎调整系统设置 https://github.com/itsfatduck/optimizerDuck 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰 #Windows优化 #系统工具 #隐私保护 #开源项目 #GitHub #Windows #WPF #NET

Showing the 12 most recent of 19 posts we hold for @i_chl. 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

Citation-graph rank — 127,832 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 8 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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Fᴜғᴜ の Cʜᴀɴɴᴇʟ” (@i_chl), 764 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/i_chl.

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.