Telegram RegisterThe public register of Telegram

Channel

今日份koipy

@koipyc

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

193subscribers

+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-1002361606266
TypeChannel
Username@koipyc
Description一个代理平台的测试工具(Telegram Bot) 此频道发布koipy程序包、更新日志 koipy文档: https://koipy.gitbook.io/koipy
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/koipyc

Growth

192193192.57 Aug 2026, 22:31 — 192 subscribers8 Aug 2026, 11:18 — 193 subscribers8 Aug 2026, 11:49 — 193 subscribers7 Aug 2026, 22:318 Aug 2026, 11:49
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 192–193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:49193no change
8 Aug 2026, 11:18193+1
7 Aug 2026, 22:31192first reading

Engagement

11 posts held, back to 30 July 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
86.6%
avg views ÷ 193 subscribers
Avg views / post
167
6 posts measured
Reaction rate
2.70%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 6 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 6 August 2026
Posts held11 (30 July 20266 August 2026)
Views total1,003
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:49 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
11
Links
29

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

5 reactions across 1 post, in 2 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍480.0%
🥰120.0%

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

Measured over the 11 most recent posts we hold, published 30 July 2026 to 6 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.

Recent posts

6 Aug 2026, 14:09 UTC95 viewsread 8 August 2026

🔔Koipy v2.1.0-dev 发布包 ⬆️更新日志: 1. 清理并优化冗余代码 2. 访客模式的内联键盘代码实现同步 3. 又又又重构了任务构建流程的代码,使其可维护性更高,已最大程度解耦各个模块(我已燃尽) 4. 修正了配置模板(config.example.yaml)的一处书写错误 5. 修正了v2ray logo文件没有打包进去的问题 6. koipy v2.1.0-dev-e03a0a (2026-08-04) 1. 修复访客模式的后端翻页功能 2. 访客模式下未找到规则时不再报错后取消任务,而是会静默跳过(回退到与普通消息模式一致) 3. 将 slave.mwss 字段更正为 slave.mtls ,功能不变 koipy v2.1.0-dev (2026-08-02) 🎉更新内容: 1. 实现了在访客模式(Guest mode)下进行完整的节点测试功能 2. 鉴权模块适配访客模式 3. 解析指令模块

2 Aug 2026, 11:23 UTC185 views5 reactionsread 8 August 2026
Photo

🎉 新功能预告:访客模式 访客模式 (Guest Mode) 访客模式允许您在公开群组、私密群组及个人聊天中,通过 @机器人名字 发起节点测试。您可随时随地在各类聊天场景中进行测试(机器人没有加入那个聊天群也是可以的)。 使用方法: 1. 您必须亲自前往 @BotFather 的 Mini-app 页面以启用访客模式:点击此处前往。 2. 启用访客模式后,操作逻辑与传统消息模式(以 / 开头触发测试)相似。您仅需在消息最开头 @机器人 即可,其余操作与传统模式一致,如图所示,操作十分简便 ☺️。

👍4🥰1

30 Jul 2026, 09:42 UTC213 viewsread 8 August 2026

🔔Koipy v2.1.0-dev 发布包 ⬆️更新日志: ⚠️ 由于改动过于大胆,可能非常不稳定,所以提高一个大版本号 更新内容: 1. 移除了过时脚本 2. 移除了ffmpeg相关依赖,如果需要生成video类型的结果图,根据日志提示安装第三方依赖包 3. 本地化文本颜色代码格式支持。可以在本地化文本里写颜色代码格式来让bot的按钮显示颜色,例子:https://t.me/koipyc/464 4. 现在bot按钮将默认显示颜色,如果不喜欢可以下载以前语言包进行替换 5. 修复invite按钮无法移除的问题 6. 升级部分第三方依赖的版本 7. 完全重写了整个测试任务调度系统,新版任务调度即将兼容bot的guest mode,新的代码目前正常测试中,请各位多多反馈一下存在的问题 8. 修复了HTTP回调时的请求头,优化了代码 9. 优化了配置文件序列化模块(这也可能不稳定,目前正在测试) 10. 序列化模块支持了现代的

Showing the 11 most recent of 11 posts we hold for @koipyc. 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 — 635,335 of 1,169,250entries 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

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

“今日份koipy” (@koipyc), 193 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/koipyc.

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.