Channel
@TreascTestChannel
On this record: Growth · Engagement · Posts · Citations · Cite this entry
718subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003093892833 |
|---|---|
| Type | Channel |
| Username | @TreascTestChannel |
| Created | Between 1 August 2025 and 24 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/TreascTestChannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:36 | 718 | -1 |
| 8 Aug 2026, 02:15 | 719 | no change |
| 7 Aug 2026, 17:03 | 719 | first reading |
5 posts held, back to 24 August 2025 — 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 5 posts for this entry, the most recent from 31 May 2026. An engagement rate over an empty window would be a number about nothing.
机器人已重写完成，目前支持多并发测试，新增PING、TCPING、CIDR PING、CIDR TCPING、连通性测试、通用代理URL自动转换Clash配置文本。 PING 向机器人发送 192.169.122.174 TCPING 向机器人发送 192.169.122.174:80 CIDR PING 向机器人发送 192.169.122.174/24 CIDR PING 向机器人发送 [192.169.122.174/24]:80 连通性测试 向机器人发送 Clash配置文件URL、配置文件文本、YAML配置文件 连通性与测速测试 向机器人发送 Clash配置文件URL、配置文件文本、YAML配置文件
我们新增了实际的 RTT 测量，去除了 TCP 握手延迟，仅计算实际的通信延迟。 游戏都参考此延迟，因为大多数游戏使用 UDP 协议，因此没有握手延迟。
关于机器人及频道的头像，我们已经委托设计师进行设计，预计将在30天内完成并交稿。
这么好用的机器人怎么还没有人使用呢👀 我们正在寻找 V2、NS、L站和奶昔的推广合作伙伴！只需推广我们的机器人并附上使用教程，每个帖子可获得 5~10 U 的奖励。 如果您有兴趣，请联系 @TreascFounder。
🎉 欢迎体验我们自主研发的测试机器人 @TreascTestBot 图生动！ 机器人基于 Clash Mihomo Core 支持多种主流协议。 我们非常重视您的隐私，机器人采用无状态运行模式，后端不会保存您的订阅链接、配置文件或节点信息。 您无需在群内进行测试，以免泄露节点信息等隐私。只需关注频道并加入群组，即可通过私聊使用机器人。
Showing the 5 most recent of 5 posts we hold for @TreascTestChannel. 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 — 292,647 of 1,480,944entries 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.
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.
Named by 1 registered channel — 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“TreascTest | 公益测试机器人” (@TreascTestChannel), 718 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/TreascTestChannel.
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.